Install Jentic One Beta

Connect the The Futures API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Futures API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthefutures.io%2Fthefutures" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthefutures.io%2Fthefutures" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with The Futures API.

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

GET STARTED

Start building with The Futures API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'validate token credentials', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — the futures api provides endpoints for authentication, managing tickets (creative design requests), retrieving available features/wizards, and accessing ticket files.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using The Futures API through Jentic.

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.

The Futures API

Name: The Futures API
Brand: The Futures API
Availability: InStock

Community OpenAPI document · agent-readyMediaAudio Processingbearer5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically validate token credentials, get available wizards. Covers 5 operations with bearer authentication.

Use for: I need to validate token credentials, I want to available wizards, Search for a ticket, Find all tickets

Not supported: Does not handle payments, communications, or crm - use for media and content only.

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.

Jentic One on Github View OpenAPI Document

Connect the The Futures API to your agent

Capabilities

Start building with The Futures API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

The Futures API