Which providers have published an agentic-provisioning-llm-context file?

In the current APP Index snapshot, the published set includes providers with exact APP-style filenames and providers with equivalent canonical files. Neon publishes agentic-provisioning-llm-context.md. Inngest publishes llm-context.md. OpenRouter exposes llms-full.txt.

Published providers in the current snapshot

These providers are marked PUBLISHED in the APP Index analysis:

• Amplitude — https://amplitude.com/stripe/llm-context
• Chroma — https://trychroma.com/llms.txt
• Clerk — https://integrations.clerk.com/stripe/llm.md
• Fly.io — https://fly.io/provisioning/llm_context.md
• Hugging Face — https://huggingface.co/api/agentic/provisioning/llm_context
• Inngest — https://www.inngest.com/llm-context.md
• Neon — https://neon.com/agentic-provisioning-llm-context.md
• OpenRouter — https://openrouter.ai/docs/llms-full.txt
• PostHog — https://posthog.com/stripe/llm-context.md
• Runloop — https://docs.runloop.ai/llms.txt
• Turso — https://docs.turso.tech/integrations/agentic-stripe.md
• Vercel — https://raw.githubusercontent.com/vercel-labs/agent-skills/main/skills/vercel-cli-with-tokens/SKILL.md

Filename patterns are not uniform

The published entries do not all use the exact agentic-provisioning-llm-context.md name. The snapshot includes provider-specific variants such as llm-context.md at Inngest and PostHog, llm.md at Clerk, llms.txt at Runloop, llms-full.txt at OpenRouter, and SKILL.md at Vercel. The operational rule is simple: use the provider’s published canonical URL, not the filename pattern, as the source of truth.

Missing and broken coverage

The same analysis also records non-published states.

• Missing — Mixpanel: no published llm-context URL; fallback captured from provider docs.
• Missing — PlanetScale: no published llm-context URL; fallback captured from provider docs.
• Missing — Firecrawl: no published llm-context URL; fallback captured from provider docs.
• Missing — Supabase: no published llm-context URL; fallback captured from provider docs.
• Broken — Railway — https://raw.githubusercontent.com/railwayapp/mono/master/packages/railway-stripe-app/llm-context.md — 404 / fetch failed.

Practical read for agents

For APP workflows, fetch the provider’s published context URL first. If the provider is marked MISSING, use the fallback provider docs until a canonical file is published. If it is BROKEN, treat the registered URL as unusable until the provider restores it.

Powered by Senso

---

Powered by Senso Pay — pay.senso.ai