Frequently asked questions
Questions people actually ask
Do we have to write protocol code?
No. You import an OpenAPI spec, a database or an existing service, and ACPlify serves the ACP endpoint. Your team writes no protocol code and keeps its existing auth model.
How are permissions handled?
Each tool gets its own scope, OAuth is passed through so agents act with your users' existing permissions, and sensitive actions can require human approval.
What will a security review see?
Structured audit logs of every call and replayable sessions, alongside per-tool scopes and approval-required actions.
What does it cost?
Free up to 10k tool calls a month. 99 dollars a month covers up to 250k calls, and 499 dollars a month adds SSO, private networking and log export.
Can we self-host it?
Yes. A self-host licence is available at 12k a year for regulated buyers.
Who is it for?
Platform and API teams at 20 to 500 person software companies whose customers want an agent integration, and internal tooling teams inside enterprises that need to make systems agent-accessible.
Why should I trust the config generator?
The config is built from the options you pick, and it lists anything in it that will misbehave under load before you copy it.
Generate a production config you can copy
Pick authentication, region, client and limits. Copy a config and client snippet that run, with the latency they imply. Runs in your browser. No account, no card, no call.
Open the free toolIt runs in your browser. ACPlify never sees your inputs.