Problem
No explicit runtime contract
Without machine-readable discovery and typed routes, agent behavior depends on undocumented assumptions.
Execution layer | typed capabilities | machine-readable runtime
AgentDoor turns declarations into a working runtime: discovery files, typed capability routes, sessions, rate limits, optional AI policy publication, and optional audit artifacts.
AgentDoor is the execution layer for agent-readable websites.
What It Is
AgentDoor provides explicit discovery endpoints and typed capability execution routes so agents can operate against a stable contract.
It includes session handling, policy-aware access controls, and optional audit outputs for teams that need stronger operational guarantees.
Why It Exists
Problem
Without machine-readable discovery and typed routes, agent behavior depends on undocumented assumptions.
Failure mode
Scraping and ad hoc integration logic break when interfaces or flows change.
Response
AgentDoor publishes stable capability contracts, session flow, and policy hints for reliable machine interaction.
How It Works
1
Define site metadata and capabilities with clear machine-facing semantics.
2
Serve discovery endpoints and capability route contracts at well-known paths.
3
Run typed capability calls with sessions, auth controls, and rate limits.
4
Apply optional AI policy and produce optional audit artifacts for verification.
Quickstart
Start with the SDK package and register your first coordinated capability surface.
npm install @agentdoorio/sdk @agentdoorio/express
import { AgentDoor } from "@agentdoorio/sdk";
const door = new AgentDoor({
service: "example-api",
repo: "github.com/your-org/your-repo"
});
await door.connect();
await door.publishCapabilities();
Contact
AgentDoor is for organizations that want explicit, typed, machine-readable interaction surfaces instead of brittle automation.