canonical: https://jentic.com/apis/thefutures.io/thefutures # The Futures API The Futures API provides endpoints for authentication, managing tickets (creative design requests), retrieving available features/wizards, and accessing ticket files. The API exposes 5 endpoints secured with bearer authentication. ## For AI agents Programmatically validate token credentials, get available wizards. Covers 5 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for media and content only. ## Capabilities - Validate token credentials - Get available wizards - Create a ticket - Query and filter The Futures API records by parameters - Monitor The Futures API operational status and events ## Use cases ### Media and Content Operations Use the The Futures API to perform media operations programmatically. The API provides 5 endpoints covering core functionality including validate token credentials, get available wizards, create a ticket. Example prompt: Call POST /auth-webhook to validate token credentials ### Automated Auth Management Automate auth operations by combining multiple The Futures API endpoints. Agents can get available wizards and then create a ticket in a single workflow. Example prompt: Call GET /features to get available wizards, then verify the result ### AI Agent Integration via Jentic AI agents discover and call The Futures API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually. Example prompt: Search Jentic for 'validate token credentials', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/auth-webhook` | Validate token credentials | | GET | `/features` | Get available wizards | | POST | `/tickets` | Create a ticket | | GET | `/tickets` | Get tickets | | GET | `/tickets/files` | Get ticket files | ## Key resources - **Auth** — Operations related to Auth - **Features** — Operations related to Features - **Tickets** — Operations related to Tickets ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 69 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/thefutures.io/thefutures/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring The Futures API by hand means learning its bearer auth against gwy.thefutures.io and handling its webhook, feature, and ticket endpoints yourself. Through Jentic you install once, import The Futures API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The Futures API keeps ticket and webhook targets in the request body on endpoints like /tickets and /auth-webhook, so limit the agent to the operations it needs, such as listing features or creating a ticket. You choose that set, so an operation is only reachable if you include it. - **Credential handling:** Your Futures API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a ticket' or 'list available features', and Jentic returns the matching Futures API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Cloudinary** — Alternative media API - **Mux** — Alternative media API ## FAQ ### What authentication does the The Futures API use? The The Futures API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I validate token credentials with the The Futures API? Yes. Use the POST /auth-webhook endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the The Futures API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I validate token credentials through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate token credentials'. Jentic returns the matching The Futures API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the The Futures API have? The The Futures API exposes 5 endpoints covering auth, features, tickets operations. ### Can I limit what my agent is allowed to do with the The Futures API? Yes. Jentic One is self-hosted, so you set the rules for which of The Futures API operations your agent may call, from validating token credentials on /auth-webhook and listing features on /features to creating or reading tickets on /tickets and fetching files on `/tickets/files.` Because ticket and webhook targets live in the request body, an operation is reachable only when you include it in the set you grant, so you can allow an agent to list features or create a ticket while withholding everything else. Your stored bearer token is injected at execution time and never enters the agent's prompt or context.