CVE Vulnerability Search: NVD records with exploit status changelog

https://apify.com/llms.txt

+ - Don't guess Actor IDs or API paths: a guess returns a 404. Take the ID from Store search: use the result's `id`, or join `username` and `name` as `username~actor-name` in API URLs. The owner is often not `apify` (Google Maps is `compass/crawler-google-places`). An Actor's input schema is in `data.actorDefinition.input` of `GET https://api.apify.com/v2/actors/{username}~{actor-name}/builds/default`, with no token needed for a public Actor.+ - If a request fails because nobody is signed in, including a 402 that offers x402 payment, tell the user how to fix it instead of stopping: connect https://mcp.apify.com and sign in through the browser first; otherwise create a token at https://console.apify.com/settings/integrations and set it as an environment variable rather than pasting it into chat.

https://apify.com/llms.txt

− - [Apify agentic resource catalog](https://apify.com/.well-known/ai-catalog.json): Agentic Resource Discovery (ARD) catalog of the resources an agent can call or read — the MCP server, the REST and Store search APIs, each Agent Skill, the agentic payment path, and the markdown documents describing the agent quickstart, the Store and pricing.+ - [Apify agentic resource catalog](https://apify.com/.well-known/ard.json): Agentic Resource Discovery (ARD) catalog of the resources an agent can call or read — the MCP server, the REST and Store search APIs, each Agent Skill, the agentic payment path, and the markdown documents describing the agent quickstart, the Store and pricing.

https://apify.com/llms.txt

− - [auth.md](https://apify.com/auth.md): Preview registration flow for agents to authenticate with Apify without a sign-up form.+ - [auth.md](https://apify.com/auth.md): How an agent gets an Apify credential — the live OAuth device flow, MCP browser sign-in, API tokens, and prepaid tokens. Apify does not support agentic self-registration.