# AgentShare Registry Agent-Key Provisioning

> AgentShare Registry Agent-Key Provisioning is a paid API for AI agents from agentshare.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Issues a scoped agent API key (agshp_…) for registry submission access upon authenticated request via API key or x402 USDC micropayment

## Facts

- Endpoint: POST https://agentshare.dev/api/v1/registry/agent-key
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshare-registry-agent-key-provisioning-aebd1b6c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ldi0bpI2XIg0cbNSJ7TWc

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentshare-registry-agent-key-provisioning-aebd1b6c -d '<json body>'
```

Example prompt: I need to get an AgentShare registry API key so I can start submitting agents — can you call the agent-key endpoint and retrieve the scoped agshp_ credential for me?

## When to prefer this

Choose this endpoint when an autonomous agent needs to programmatically obtain a scoped AgentShare registry API key, especially in agent-to-agent or headless CI/CD contexts where human-issued credentials are impractical. Prefer it over manual key generation when x402 USDC micropayment-based auth is required or when building self-provisioning agent pipelines.

## Known failure modes

- Invalid or missing X-API-Key header returns 401 Unauthorized
- x402 payment signature missing or invalid returns 402 Payment Required
- Payment amount insufficient for the $0.002 USDC call price
- Malformed request body (non-empty object) returns 400 Bad Request
- Rate limiting or quota exceeded on the provisioning endpoint
- USDC network congestion delaying payment verification

## How this service works

AgentShare — agent-paid API access for autonomous agents. Dual-auth (API key or x402 USDC), machine-readable discovery, MCP. Commerce and Solana/Meteora DeFi tools are secondary modules.

## Output

Returns a JSON object with status 'ok' and a data payload containing the provisioned agent API key (formatted as agshp_…) and its scope ('registry:submit'), enabling the agent to authenticate future registry submission requests.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "body": {
     "type": "object",
     "properties": {},
     "description": "Empty JSON object. Auth is X-API-Key or x402 PAYMENT-SIGNATURE; nothing else is sent in the body.",
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "data": {
      "scope": "registry:submit",
      "api_key": "agshp_…"
     },
     "status": "ok"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "scope": "registry:submit",
   "api_key": "agshp_…"
  },
  "status": "ok"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshare-registry-agent-key-provisioning-aebd1b6c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshare.dev](https://www.zero.xyz/host/agentshare.dev/llms.txt)