What you get
- An API-calling agent generated from the spec: HTTP call configurations grouped by tag, the pipeline, and deployment
- Endpoint filtering, a base URL override and auth header propagation
- The option to add an MCP server's tools next to the generated ones
- Tools you can review, diff and version, because they are configuration
How it works in EDDI
- Give EDDI the OpenAPI spec through the
create_api_agentMCP tool orPOST /administration/agents/setup-api. - Allow-list the operations the agent should have. An endpoint that is not declared cannot be called.
- EDDI generates the HTTP call configurations, builds the full pipeline and deploys the agent.
- Keep credentials as
${vault:...}references. - Gate writes with
http.post:*,http.put:*,http.patch:*,http.delete:*and exempt reads withhttp.get:*.
Configuration
Taken from the EDDI documentation. Placeholders such as your-agent-id are yours to replace.
{
"targetServerUrl": "https://api.example.com/v1",
"httpCalls": [
{
"name": "list-open-orders",
"saveResponse": true,
"responseObjectName": "order",
"request": {
"method": "GET",
"path": "/orders",
"queryParams": { "status": "open" },
"headers": { "Authorization": "Bearer ${vault:orders-api-token}" }
}
}
]
}{
"hitlConfig": {
"toolApprovals": {
"requireApproval": [
"http.post:*",
"http.put:*",
"http.patch:*",
"http.delete:*"
],
"exempt": [
"http.get:*"
],
"approvalTimeout": "PT30M",
"timeoutPolicy": "AUTO_REJECT"
}
}
}Governance
- Approval patterns can address what a tool calls (
http.post:*), which stays correct when an operationId changes. - Outbound calls are protected against SSRF and path traversal by the platform.
- Through REST,
setup-apiaccepts ahitlConfig, so an agent can be provisioned with its write tools gated from the first version. The MCP tool cannot set it. - Decisions land in the audit ledger.
Good to know
- A generated write tool takes the whole request body as one
requestBodyparameter.
Need it built and run for you?
EDDI Solutions builds and maintains connectors, runs EDDI as a managed or co-operated instance, and supports you in your own cloud or on-premises.
Talk to EDDI Solutions ↗Related integrations
Configuration and behavior on this page follow the EDDI documentation, checked on 2026-10-14. Field names and defaults can change between releases, so confirm them in the docs for your version.