Practical AI systems for service businesses Explore services →

Public API / Agent access / v1

The Future Studio
Developer Resources.

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

Start with the
right file.

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.

Public API

One stable,
read-only route.

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.

GET

Site context

Returns verified public company, audience, service, market, safety and navigation information.

GET https://thefuturestudio.online/api/v1/site-context Accept: application/json
JSON

Error format

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/." }
60

Rate limits

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

Versioned for
safe change.

Major versions are carried in the URL path. Version v1 is active and is not scheduled for deprecation or shutdown.

01

Stable major versions

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.

02

Minimum notice

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.

03

Runtime signals

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.

04

Legacy alias

/api/site-context remains a compatibility alias for v1. New integrations should use /api/v1/site-context. No removal date is currently assigned.

Public boundary

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.