AgentOnboard
How it works

Your integration is
one verify call.

Here is exactly what it costs to make your API agent-native: drop in the SDK, agents present their ID card, you verify through us, and the agent acts for its user.

The flow

Four steps, from their side

01
Drop in the SDK
Install @agentonboard/sdk (or call POST /api/verify directly). One dependency, no OAuth flows, no token management to build. Your platform becomes agent-native.
02
Agents present their ID card
A user's agent authenticates once through AgentOnboard and receives a short-lived session token. On every API call, the agent presents that token instead of a static key.
03
You make the verify call
Your API sends the session token to AgentOnboard and gets back who the agent represents — the user's verified email. That's the entire integration: one call.
04
The agent acts for its user
The agent calls your API on behalf of its user, and every interaction lands in your audit log — which agent, which user, how often, whether it succeeded.
The code

The entire integration

verify.ts@agentonboard/sdk
import { verify } from "@agentonboard/sdk";

// one call — that's the whole integration
const result = await verify(partnerKey, sessionToken);

if (result.ok) {
  const email = result.email; // who the agent represents
  // look up the user and let the agent act
} else {
  // deny: expired token, revoked key, unknown agent
}
The trade-off

What you build, and what you never build

You build
One integration, once.
  • One verify call in your request path
  • Map the verified email to your user account
  • Let the agent act, with your normal authorization rules
You never build
The plumbing that burns provider teams.
  • OAuth flows for every agent platform
  • API-key issuance, storage, or rotation
  • Per-user setup for each agent your users run
  • Token expiry or refresh logic

Ship it this afternoon.

Free during early access. No credit card required. One verify call.

Start integrating free