zeroid

Manage agent identities and credentials via a REST API.

155|18|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/highflame-ai/zeroid --skill zeroid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeroid
Source: https://github.com/highflame-ai/zeroid/tree/main/examples/claude-skill
Command: npx skills add https://github.com/highflame-ai/zeroid --skill zeroid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When autonomous agents act on behalf of users or other agents there is no reliable, auditable way to prove who performed an action and under what delegated authority; Zeroid provides cryptographically verifiable identities, short-lived credentials, and real-time revocation to restore clear accountability and secure delegation flows.

Core Features & Use Cases

  • Agent Identity Management: Register agents and assign SPIFFE/WIMSE URIs with one-time API keys and optional public keys for JWT assertions.
  • OAuth 2.1 Token Issuance & Delegation: Issue access tokens via api_key, client_credentials, jwt-bearer, authorization_code, refresh, and perform RFC 8693 token-exchange to delegate limited scope to sub-agents.
  • Governance and Revocation: Create credential policies (TTL, allowed scopes, max delegation depth), introspect tokens, and revoke tokens or API keys immediately across delegation chains.
  • Use Case: Employ Zeroid to provision unique agent identities for a CI pipeline, delegate limited runtime permissions to ephemeral worker agents, and revoke access instantly if a worker is compromised.

Quick Start

Use the zeroid skill to register an agent, save the returned API key securely, and request an access token for that agent.

Frequently Asked Questions about zeroid

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage OAuth 2.1 token delegation for autonomous agents?

Manage OAuth 2.1 token delegation by registering agents and using RFC 8693 token-exchange to issue limited-scope access tokens to sub-agents. This provides cryptographically verifiable identities and auditable delegated authority.

What is RFC 8693 token-exchange and when do I need it for agent workflows?

RFC 8693 token-exchange is a mechanism to delegate limited permissions by trading an existing access token for a new one with restricted scope. You need it when autonomous agents or ephemeral workers act on behalf of users or other agents.

Can I issue SPIFFE identities and API keys for multi-tenant agent deployments?

Yes, you can issue SPIFFE/WIMSE URIs and one-time API keys for registered agents. Multi-tenant administration is supported via tenant headers on admin routes to separate identity and credential policy enforcement.

How do I revoke delegated OAuth tokens across an entire delegation chain?

Revoke delegated OAuth tokens instantly by triggering token or API key revocation workflows. This immediately invalidates credentials across the entire delegation chain to restore accountability if a worker agent is compromised.

What credential policies can I enforce for autonomous agent token issuance?

Enforce credential policies by setting constraints such as maximum TTL, allowed scopes, and maximum delegation depth. These policy-enforced limits govern OAuth 2.1 token issuance and RFC 8693 token-exchange operations.

Does this approach support jwt-bearer assertions and authorization_code grants?

Yes, OAuth 2.1 token issuance supports api_key, client_credentials, jwt-bearer, authorization_code, and refresh grants. Agents can use registered public keys to sign JWT assertions for authentication.