SaaS
IntentChain operates the control plane and gateway as a managed execution service.
Best for teams that want the governed execution rail without managing deployment, routing, or gateway operations themselves.
IntentChain is the centralized, exclusive execution path for any AI agent action with economic impact and high-risk operation.
We are the guardrail between agent intent and real-world impact. When AI agents touch money or sensitive systems, the request is centrally validated, policy-checked, bound to a single-use permit, and only then executed exclusively through our gateway.
Put the money-moving call on a controlled execution path, not behind an agent runtime wrapper.
// Agent requests a $5,000 payment through IntentChain
POST /v1/payment
Authorization: Bearer sk_live_…
X-Agent-ID: wire-transfer-agent
{
"from": "acct_8832",
"to": "acct_4421",
"amount": 5000,
"currency": "USD"
}
// → Authenticated. Policy-evaluated. Permit bound. Executed via gateway.
{ "status": "completed", "charge_id": "ch_9f3a" }
Most agent governance tools sit beside the agent runtime. IntentChain sits on the mutation path: supported actions are schema-validated, policy-required calls need a signed permit, and unsupported or changed requests never reach the downstream system.
IntentChain is designed for two deployment flavors: managed SaaS for fast rollout, and Enterprise self-hosted for teams that want the gateway under full customer control behind private VNets while keeping the same permit and policy model.
IntentChain operates the control plane and gateway as a managed execution service.
Best for teams that want the governed execution rail without managing deployment, routing, or gateway operations themselves.
IntentChain keeps the control plane, while the execution gateway runs inside the customer's private network boundary.
For regulated or high-custody deployments, the customer runs the gateway behind private VNets and keeps routing, network enforcement, and credential custody under their own control.
Watch a governed request move from authentication and policy to permit binding, credential mediation, execution, and receipt logging.
We sit in front of the target API, not beside the agent runtime. That placement changes everything: the protected mutation has to pass through IntentChain before it can ever reach the downstream system.
IntentChain is for actions that need hard guarantees, not just runtime advice.
Integrate with any agent runtime using HTTP. The agent talks to IntentChain, never directly to the protected downstream action.
import httpx
async def transfer_funds(from_acct, to_acct, amount, currency="USD"):
# Agent has NO downstream credentials — only an IntentChain API key
async with httpx.AsyncClient() as client:
response = await client.post(
"https://intentchain.ai/v1/payment",
headers={
"Authorization": f"Bearer {API_KEY}",
"X-Agent-ID": "wire-transfer-agent",
},
json={
"from": from_acct,
"to": to_acct,
"amount": amount,
"currency": currency,
},
)
# IntentChain handles the protected execution path:
# Auth → Policy eval → Permit → Credential mediation → Forward → Receipt
return response.json()
# The agent never sees bank credentials.
# The agent cannot change the amount after policy approval.
# The gateway records a structured execution receipt.
{
"name": "wire-transfer-limits",
"canonical_action": "money.payment",
"rules": [
{
"field": "amount",
"operator": "lte",
"value": 25000,
"on_fail": "deny"
},
{
"field": "agent_daily_total",
"operator": "lte",
"value": 250000,
"on_fail": "deny",
"message": "Agent daily ceiling exceeded"
}
],
"resolution": "deny-wins"
}
// Deny-wins: if ANY rule fails, the action is blocked.
// No LLM in the decision path — deterministic evaluation.
# Wire transfer through IntentChain gateway
curl -X POST https://intentchain.ai/v1/payment \
-H "Authorization: Bearer sk_live_AbCdEf..." \
-H "X-Agent-ID: wire-transfer-agent" \
-H "Content-Type: application/json" \
-d '{
"from": "acct_8832",
"to": "acct_4421",
"amount": 5000,
"currency": "USD"
}'
# Response (transparent — same as downstream API)
{
"charge_id": "ch_9f3a",
"amount": 5000,
"currency": "USD",
"status": "completed"
}
Five common failure modes. Three control models. Only one controls the mutation path.
| Attack vector | Raw credentials | Policy middleware | IntentChain |
|---|---|---|---|
|
Direct HTTP call outside the framework hook
Uninstrumented SDK or raw client path
|
✕ Direct call executes | ~ Missed if outside hook | ✓ No protected path except the gateway |
|
Approved request is changed before execution
Payload differs from what policy approved
|
✕ Executed as sent | ~ Depends on where approval runs | ✓ Permit hash mismatch → blocked |
|
Agent replays the same payment 10×
Same request repeated
|
✕ 10 executions succeed | ~ Retry behavior varies by app | ✓ Single-use permit rejects replay |
|
Credential theft from the agent runtime
Container or memory compromise
|
✕ Full downstream access | ~ Still exposed if creds live in runtime | ✓ Agent holds no downstream creds |
|
Unsupported endpoint or schema drift
Action not in an approved native or mirrored profile
|
✕ Downstream decides | ~ Depends on adapter coverage | ✓ Denied by default |
Start where non-bypass control matters most: payments, transfers, refunds, and high-impact account mutations across business systems.
AI support agents issuing refunds, processing chargebacks, and adjusting billing. Every action is financially irreversible — a rogue agent means real money lost.
Banking agents moving money between accounts, approving loan applications, and updating customer KYC records. Regulated, audit-critical, and zero-tolerance for errors.
Enterprise AI automating account lifecycle — provisioning, tier changes, billing adjustments, and configuration mutations across Salesforce, Zendesk, and internal systems.
Healthcare AI handling appointment scheduling, prescription renewals, billing disputes, and patient record updates. Compliance-heavy with strict audit requirements.
Start with one governed payment, transfer, refund, or account mutation.
No downstream credentials in the agent runtime. No protected mutation outside the gateway.