1Password (Events API) integration for AI agents.
1Password (Events API) integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves 1Password (Events API) tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real 1Password (Events API) actions, managed and audited.
Your user connects 1Password (Events API) once; your agent can then query 1Password audit events, item usage, and sign-in attempts — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants 1Password (Events API) access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported 1Password (Events API) tools.
8 tools are generated from the published 1Password (Events API) catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 8 tools. All published catalog entries are included in this page's server-rendered HTML.
- Retrieves audit events for actions performed by team members within a 1Password account
- This endpoint requires your JSON Web Token to have the *auditevents* feature.
- api-v1
- Retrieves audit events for actions performed by team members within a 1Password account
- This endpoint requires your JSON Web Token to have the *auditevents* feature.
- api-v2
- Performs introspection of the provided Bearer JWT token
- Performs introspection of the provided Bearer JWT token
- auth
- Performs introspection of the provided Bearer JWT token
- Performs introspection of the provided Bearer JWT token
- auth
- Retrieves events for each usage of an item stored in a shared vault within a 1Password account
- This endpoint requires your JSON Web Token to have the *itemusages* feature.
- api-v1
- Retrieves events for each usage of an item stored in a shared vault within a 1Password account
- This endpoint requires your JSON Web Token to have the *itemusages* feature.
- api-v2
- Retrieves events for both successful and failed attempts to sign into a 1Password account
- This endpoint requires your JSON Web Token to have the *signinattempts* feature.
- api-v1
- Retrieves events for both successful and failed attempts to sign into a 1Password account
- This endpoint requires your JSON Web Token to have the *signinattempts* feature.
- api-v2
1Password (Events API) integration, answered
- How do AI agents use 1Password (Events API) through Open Connector?
- Your user connects 1Password (Events API) once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes 1Password (Events API) tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a 1Password (Events API) MCP server?
- Yes. Open Connector can serve 1Password (Events API) as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call 1Password (Events API) actions with credentials injected server-side.
- Where do 1Password (Events API) credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents 1Password (Events API) — keep the keys.
Open source, self-hostable, with 1Password (Events API) credentials that never leave your infrastructure. Run it from source today.