Security
Three layers of permission behind every tool call
Your configuration, your user's authorization and the provider's own rules. How Agent200 decides whether a tool may run, and the controls underneath.
2 min read
Blog
oauth
Guides
Managed OAuth for AI agents: who authorizes what
An Agent200 API key lets your app call Agent200. It does not open anyone's inbox. How developer configuration, end-user authorization and provider permissions fit…
2 min read
Engineering
Every agent rebuilds the same plumbing. It doesn’t have to.
Integrations, OAuth, tool schemas, credentials and a bill per provider: the work around an AI agent repeats from project to project. Here is that…
2 min read
Use cases
Build a daily brief agent, step by step
The hello world of useful agents: a morning summary from each user's own messages and email. The whole path, from project setup to scheduling.
2 min read
Engineering
Designing agents for many users from day one
A demo has one user. A product has thousands, each with their own accounts. How per-user connections work, and four rules for your side.
2 min read
Guides
From prototype to production in eight steps
From first key to first real user: the eight steps of shipping an agent with Agent200, and a checklist before anyone else depends on…
2 min read
Guides
Connection prompts users say yes to
Agent200 handles the OAuth mechanics. What the user sees is up to you. Ask at the moment of need, say what the agent will not do, and ask for less.
2 min read
200 OK
Build the agent.
Access everything it needs.
Bring the agent you already have. Agent200 provides and executes its external capabilities.