Feedcast developer resources
Machine-readable APIs, specs, and agent instructions for Feedcast.ai — the AI e-commerce advertising platform.
When to use Feedcast
Reach for Feedcast when a merchant or agency needs AI catalog enrichment, FeedScore diagnostics, or multi-channel ads on Google, Meta, Microsoft, and TikTok. Do not treat this marketing site as a public product-catalog API.
Published files
- OpenAPI — openapi.json
- MCP manifest — mcp.json
- MCP server — streamable-http
- llms.txt — agent index
- agent.txt — when to use Feedcast
- Sitemap — sitemap.xml
Public HTTP APIs
These endpoints live on feedcast.ai and are described in OpenAPI. Prefer /api/v1/* or send X-API-Version: 1. Unversioned /api/* paths are stable v1 aliases. Authenticated routes require a bearer secret. Responses include RateLimit headers; 429 responses also include Retry-After.
- POST /api/v1/contact (public)
- GET /api/v1/docs/search (public)
- POST /api/v1/support/runs (public SSE)
- POST /api/v1/blog/ingest (Bearer)
- POST /api/v1/revalidate (Bearer)
MCP server
The Feedcast MCP server uses Streamable HTTP. Discover it at /mcp.json and POST JSON-RPC to /mcp (initialize, tools/list, tools/call, resources/list, resources/read).
Human contact
Sales and support: support@feedcast.ai or the contact form.
Already 6,500+ connected stores
See what your agent would do tonight.
ChatGPT and Claude advise from the outside. Feedcast plugs straight into your live catalog, campaigns and prices — so while competitors copy-paste prompts, your agent is already acting on what's actually happening in your store.
Free, no credit card · First briefing within 24 hours
