Stop asking users for raw API keys.
Agent Consent Flow lets users approve exactly what an AI agent can access—without pasting raw API keys into your app.
Stripe Payment Monitor
Verified PublisherMonitors failed payments and opens a GitHub issue automatically.
Requesting access to
Approve specific service keys for this application's runtime. Its host receives those keys. Disconnecting stops future retrieval, but does not invalidate keys already received.
Hosted consent screen for registered applications.
The API key copy-paste problem.
If you build an AI tool today, getting access to a user's data usually means asking them to copy a raw API key from Stripe or GitHub and paste it into your settings page. It's a massive friction point, it violates least-privilege, and it forces you to take on the liability of storing their secrets.
High user friction
Users hate hunting for API keys. It breaks them out of your onboarding flow and asks for an unreasonable level of trust before they've even used your product.
Massive over-permission
Most API keys grant root-level access. A tool that just needs to read issues shouldn't have the power to delete repositories, but raw keys rarely allow granular scoping.
Your liability
When users paste their keys into your app, you are now responsible for securing them. If your database is compromised, your users' infrastructure is compromised.
A better way to get access.
Agent Consent Flow uses signed requests, authenticated approval, one-time code exchange, and revocable opaque tokens. Explicitly approved SDK connections can retrieve provider keys; this is not a credential-hiding proxy.
Register exact boundaries
Register an ES256 public key, exact callbacks, and the maximum scopes your client may request.
Sign each request
Use a short-lived signed request, unique ID, callback state, and S256 PKCE challenge.
Users review access
Let users inspect every requested scope before an authenticated approval decision.
Exchange and verify
Exchange a one-time code for an opaque token, then introspect its active scopes at runtime.
Bounded authorization
Designed for explicit consent
Each request declares its identity, callback, and maximum scopes. Users review the requested access before Gazebo issues a revocable, scoped token.
What Agent Consent Flow provides
Explicit access approval
Users approve specific service keys before the SDK retrieves them. The application's runtime and its host receive those keys.
One-click revocation
Revoking a grant stops future retrieval and renewal. It does not erase keys already delivered; those may need rotation at the provider.
Full transparency
The hosted consent screen makes every requested scope visible before approval, and expansion always requires a new decision.
Build a signed consent flow.
Register your application in Gazebo, keep your signing key on your server, and integrate the complete request, approval, callback, renewal, and revocation flow.