Official vendor OpenAPI document · agent-readySecuritySecrets Managementbearer9 EndpointsREST
For Agents
Proxy authenticated HTTP calls to any upstream API through a stateless broker that injects stored credentials at the edge, so agent code never holds the secret. Returns the upstream response or a polling link for long calls.
Use for: Call an upstream API without handling its credentials, Forward a request to a third-party API through the broker, Proxy a write to an upstream service securely, Check whether the broker is ready to accept traffic
Not supported: Does not store credentials, define permission rules, or register upstream APIs. Use for forwarding authenticated requests to upstream APIs only.
The Broker API is a stateless data-plane proxy that forwards any HTTP request to an upstream API with the caller's stored credentials injected at the edge. The caller sends the upstream URL as the request path, and the Broker forwards the method, headers, and body unchanged, returns the upstream response synchronously, or falls back to a 202 with a polling link for long-running calls. Because secrets are injected at the proxy, they stay off the agent and the end-user device, outbound traffic has one auditable egress point, and upstream credentials rotate centrally without redeploying callers.
Install Jentic One Beta
Connect the Broker API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Broker 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.
1
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%2Fjentic.com%2Fjentic-one-broker" | sh2
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%2Fjentic.com%2Fjentic-one-broker" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Broker API.
Forward read requests to an upstream API with the caller's credentials injected at the proxy
Forward write requests to an upstream API without exposing the secret to agent code
Return the upstream response synchronously, or a 202 polling link for long-running calls
Route all outbound API traffic through one auditable egress point
Probe service health with a liveness check
Check saturation-aware readiness before sending traffic
Use Cases
Patterns agents use Broker API for, with concrete tasks.
★ Agent calls third-party APIs without touching secrets
An AI agent needs to call several third-party APIs but should never see their credentials. The Broker API injects each upstream credential at the proxy, so the agent sends only the upstream URL and payload while the secret stays on the server. Through Jentic the agent discovers the forwarding operation by intent and the credential is supplied at call time.
Forward a POST payload to an upstream API through the broker and read back the upstream response without ever holding the upstream credential
Single auditable egress point
A team wants every outbound API call from its agents to pass through one place that can be logged and controlled. The Broker API gives outbound traffic a single choke-point: it forwards method, headers, and body unchanged, so existing upstream integrations keep working while every call is observable from one spot.
Route an upstream GET through the broker so the call is captured at the central egress point and the response is returned unchanged
Long-running upstream calls
Some upstream operations take longer than a synchronous request can wait. The Broker API returns the upstream body with a 200 for fast calls and falls back to a 202 with a polling link for slow ones, so an agent can start the work and poll for the result instead of holding a connection open.
Forward a slow upstream request, receive the 202 polling link, and poll until the upstream result is ready
Key Endpoints
9 endpoints — the broker api is a stateless data-plane proxy that forwards any http request to an upstream api with the caller's stored credentials injected at the edge.
METHOD
PATH
DESCRIPTION
GET
/{upstream_url}
Execute a GET against an upstream API
POST
/{upstream_url}
Execute a POST against an upstream API
PUT
/{upstream_url}
Execute a PUT against an upstream API
DELETE
/{upstream_url}
Execute a DELETE against an upstream API
GET
/health
Service health probe
GET
/ready
Saturation-aware readiness probe
GET
/{upstream_url}
Execute a GET against an upstream API
POST
/{upstream_url}
Execute a POST against an upstream API
PUT
/{upstream_url}
Execute a PUT against an upstream API
DELETE
/{upstream_url}
Execute a DELETE against an upstream API
GET
/health
Service health probe
GET
/ready
Saturation-aware readiness probe
Jentic AI Readiness Score
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.
B
Broker API
- AI-Ready (A)85/100
100
Foundational Compliance85
Developer Experience & Jentic Compatibility90
AI-Readiness & Agent Experience94
Agent Usability60
Security82
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
85
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
44%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
97%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
90
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: ASignals: 4
86%
Description Coverage
Coverage of descriptions across API elements.
89%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
83%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
82
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
82%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring secure outbound calls by hand means building a proxy, holding upstream secrets in agent-reachable config, and handling retries and long-call polling yourself. Through Jentic you install once, import the Broker from the API Directory, store the bearer token once, and your agent proxies upstream calls through it.
Permission scoping
The Broker splits forwarding by HTTP method, so you choose which methods the agent may proxy: a rule can allow read forwarding and withhold delete forwarding. You decide the operation set, so destructive forwards are not included unless you add them.
Credential isolation
Your Broker bearer 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 'call an upstream API with injected credentials', and Jentic returns the matching Broker operation with its input schema so the agent forwards the right request without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Broker API through Jentic.
What authentication does the Broker API use?
The Broker API authenticates the caller with a bearer token, per its OpenAPI spec. The upstream credentials it injects into forwarded requests are held separately and never travel back to the agent. Through Jentic the bearer token is stored once and injected at call time, so it never enters the agent's prompt, logs, or context.
Can I forward long-running calls through the Broker API?
Yes. The Broker returns the upstream body with a 200 for fast calls and falls back to a 202 with a polling link for long-running ones, so your agent can start the work and poll for the result rather than hold a connection open. The method, headers, and body are forwarded unchanged in both cases.
Can I limit what my agent is allowed to do with the Broker API?
Yes. The forwarding operations are split by HTTP method, so a rule can allow read forwarding while withholding the delete-forwarding operation, letting the agent proxy safe calls and nothing destructive unless you add it. Every forwarded call passes the single egress point and is logged.
Is there a Broker API MCP server?
You don't need an MCP server to give your agent the Broker API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent proxies upstream calls through it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.
How do I proxy an upstream API call through Jentic?
Search Jentic for an intent such as 'call an upstream API with injected credentials' and it returns the matching forwarding operation with its input schema, so your agent sends the upstream URL and payload while the secret stays on the server. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED