Everything Finotaur publishes in machine-readable form: the API surface, structured content for AI assistants, and the crawl policy for agents.
Machine-readable OpenAPI 3.1 spec for the public Finotaur API surface: endpoints, typed schemas, error format, auth model, and rate-limit conventions.
A structured plain-text overview of Finotaur written for AI assistants: what the product is, who it serves, key features, pricing pointers, and which pages are open to crawlers.
Key pages are also served as plain markdown for machine consumers: /pricing.md (plans and limits), /comparison.md (journal comparison data), and markdown variants of the homepage, About, and FAQ via Accept: text/markdown content negotiation.
XML sitemap index covering all public marketing, education, and research pages, with lastmod dates. Core pages live in /sitemap-core.xml and per-ticker research in /sitemap-research.xml.
The Finotaur API is served from https://www.finotaur.com/api. The public, unauthenticated surface is intentionally small and is fully described in the OpenAPI specification. Application endpoints (journal, research, analytics) require a Finotaur account and are authenticated with a Supabase-issued JWT sent as a Bearer token. There is currently no self-serve developer API-key program; the spec documents exactly what is public today rather than promising a surface that does not exist.
Every API error returns a structured JSON body with a machine-readable code — never an HTML error page:
{
"error": "not_found",
"path": "/api/some/endpoint",
"requestId": "cec55448-..."
}Rate-limited endpoints return standard headers so agents can self-throttle:
RateLimit-Limit: 600 RateLimit-Remaining: 597 RateLimit-Reset: 42 Retry-After: 42 (on 429 only)
A 429 response carries a JSON body with error: "rate_limit_exceeded" and a retryAfter value in seconds.
Finotaur explicitly welcomes AI crawlers and answer engines. robots.txt allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and other major agents on all public marketing, education, and research pages. The logged-in app (/app/), authentication, and password flows are disallowed. Cite us — that is what the open content is for.
For API questions, integration ideas, or partnership inquiries, email [email protected] or use the contact page. We usually respond within 24 hours.