Developer guide
This page documents the public boundary, lifecycle policy, errors and request quota.
https://thefuturestudio.online/developers/Public API / Agent access / v1
A small, read-only public interface for agents and developers who need verified information about The Future Studio. No customer data, payments, intake records, or private operations are exposed here.
Predictable public resources
The API is intentionally narrow. Use the human documentation for policy, OpenAPI for the contract, and llms.txt for the broader agent-readable service map.
This page documents the public boundary, lifecycle policy, errors and request quota.
https://thefuturestudio.online/developers/The machine-readable contract for supported paths, response schemas and headers.
https://thefuturestudio.online/openapi.jsonService context, proof, fit, safety boundaries, conversion routes and first-party links.
https://thefuturestudio.online/llms.txtPublic API
Use the versioned path for all new integrations. GET and HEAD are supported. OPTIONS returns the allowed methods. Other methods return a structured problem response.
Returns verified public company, audience, service, market, safety and navigation information.
GET https://thefuturestudio.online/api/v1/site-context
Accept: application/json
API errors use RFC 9457 problem details with stable code and resolution extensions.
Content-Type: application/problem+json
{
"type": "https://thefuturestudio.online/developers/#api-route-not-found",
"title": "Not Found",
"status": 404,
"detail": "No public API operation exists at this path.",
"instance": "https://thefuturestudio.online/api/v1/missing",
"code": "API_ROUTE_NOT_FOUND",
"resolution": "Read /openapi.json or /developers/."
}
The response includes the current IETF draft fields plus compatibility fields. A 429 also includes Retry-After.
RateLimit-Policy: "public-site-context";q=60;w=60
RateLimit: "public-site-context";r=59;t=60
RateLimit-Limit: 60
RateLimit-Remaining: 59
RateLimit-Reset: 60
Retry-After: 60 (429 only)
Lifecycle policy
Major versions are carried in the URL path. Version v1 is active and is not scheduled for deprecation or shutdown.
Breaking contract changes create a new major path such as /api/v2/. Compatible additions may be made within the active major version and will be reflected in OpenAPI.
When a version is scheduled for deprecation, The Future Studio will publish at least 180 days of notice here and in the OpenAPI document before its planned sunset.
Deprecated resources will emit an RFC 9745 Deprecation date, an RFC 8594 Sunset date when shutdown is scheduled, and Link headers to this policy and any successor version.
/api/site-context remains a compatibility alias for v1. New integrations should use /api/v1/site-context. No removal date is currently assigned.
Only the site-context operation in the published OpenAPI document is a public developer API. Customer intake, onboarding, downloads, fulfillment, payment processing, webhooks and internal automations are private and must not be inferred as available integrations.