Machine access
Flynnstone agent access
Every public machine format reads from the same indexed-only article projection. The feeds and API never expose review material or source snapshots.
Open formats
RSS 2.0
JSON Feed 1.1
REST API discovery
REST article catalog
OpenAPI 3.1
REST examples
The Flynnstone developer quickstart and reference documents every route, schema, error, limit, cache validator, and lifecycle rule. No API key or separate sandbox is required. List up to 50 indexed articles, filter by topic, article type, or publication date, and continue with the returned opaque cursor.
curl 'https://flynnstone.ai/api/v1/articles?limit=10'
curl 'https://flynnstone.ai/api/v1/articles/butchery-roll-up-thesis'Scope and freshness
The public contract contains articles only after editorial approval and the index-state transition. Each item includes its canonical URL, publication and modification dates, claims, public source records, and any required disclosure. Strong ETags and Last-Modified validators support conditional requests. The sitemap remains the authority for indexed HTML URLs.
Errors, versioning, and deprecation
API errors use a JSON envelope with a stable machine-readable code and a human-readable message. Version 1 stays under /api/v1. A future incompatible version will use a new URL. Flynnstone will announce deprecation in this guide and send standardDeprecation and Sunset response headers before retiring a version.
Remote MCP
The read-only endpoint https://mcp.flynnstone.ai/mcp is upcoming. It will be a stateless adapter over the public REST API. Use the feeds or REST contract until the endpoint completes its separate deployment and burn-in gates.