Problem
No clear front door
Without an agent-facing surface, agents infer what they can do from pages built for people.
Discover | request | allow/deny/needs_approval | review | receipt
AgentDoor helps agents discover what they can request, applies policy, routes approval-required work to an operator, and returns an inspectable receipt.
AgentDoor makes an organization's agent-facing surface explicit, governed, and inspectable.
What It Is
AgentDoor helps agents discover what is available, ask for the right action, and receive a clear allow, deny, or escalation response.
It uses discovery files, policy-aware access controls, session boundaries, and receipts so teams can see what happened after an agent asks to act.
Why It Exists
Problem
Without an agent-facing surface, agents infer what they can do from pages built for people.
Failure mode
Requests that should be allowed, denied, or escalated are handled through brittle custom logic.
Response
AgentDoor gives agents a stable place to discover, request, follow policy, and leave records.
How It Works
1
Publish the organization, available surfaces, and agent-facing rules.
2
Give agents a structured path to ask for an action or handoff.
3
Apply policy so each request is allowed, denied, or escalated.
4
Return a receipt so teams can inspect the request, decision, and next action.
Quickstart
Start by registering the site or API that agents need to discover. Package-based SDK snippets are private-preview placeholders until the packages are published and verified.
curl -X POST https://agentdoor.io/api/register \
-H "Authorization: Bearer $AGENTDOOR_ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"slug": "example-api",
"siteName": "Example API",
"siteUrl": "https://api.example.com",
"openApiUrl": "https://api.example.com/openapi.json"
}'
Contact
AgentDoor is for organizations that want agents to use an explicit, controlled surface instead of guessing through pages, docs, forms, and APIs.