# Covenant On-Chain Identity Passport Verifier

> Covenant On-Chain Identity Passport Verifier is a paid API for AI agents from x402-seller.opencovenant.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Verifies an agent's on-chain identity passport by checking MPL Core asset ownership, 014 Registry binding, and Covenant attestation for a given asset address.

## Facts

- Endpoint: GET https://x402-seller.opencovenant.org/x402/passport/:asset
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/covenant-on-chain-identity-passport-verifier-4bb0a5d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zLR7z8gJpEyAUOHrQ-6Ao

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 covenant-on-chain-identity-passport-verifier-4bb0a5d0
```

Example prompt: Can you verify the Covenant on-chain identity passport for the MPL Core asset at address 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU — I need to confirm it has a valid 014 Registry binding and Covenant attestation before I proceed?

## When to prefer this

Use this endpoint when you need to cryptographically verify that a specific Solana-based agent or entity holds a legitimate on-chain identity passport, including MPL Core asset ownership, 014 Registry binding, and Covenant attestation — particularly before engaging in automated agent-to-agent transactions, settlements, or trust-sensitive workflows. Prefer this over off-chain identity checks when you require trustless, on-chain attestation specific to the OpenCovenant ecosystem.

## Known failure modes

- Invalid or malformed base58 asset address returns a 400 or validation error
- Asset address not found in the 014 Registry returns a negative attestation result
- Asset exists but lacks a Covenant attestation, returning an unverified status
- Network or RPC node issues may cause timeouts or 5xx errors
- Payment failure via x402 protocol results in a 402 Payment Required response

## How this service works

Observe an MPL Core asset, its 014 Registry binding, and DAS-reported AppData. This does not prove identity or claim truth.

## Output

Returns the verification result for the specified MPL Core asset, including whether the asset has a valid Covenant attestation, a confirmed 014 Registry binding, and a recognized on-chain identity passport. Typically includes asset details and pass/fail status for each component of the identity check.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "asset"
     ],
     "properties": {
      "asset": {
       "type": "string",
       "description": "MPL Core asset address (base58)"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/covenant-on-chain-identity-passport-verifier-4bb0a5d0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-seller.opencovenant.org](https://www.zero.xyz/host/x402-seller.opencovenant.org/llms.txt)