# Formo Profile Lookup

> Formo Profile Lookup is a paid API for AI agents from formo.x402.paysponge.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Retrieves a user profile associated with a blockchain wallet address from the Formo service

## Facts

- Endpoint: GET https://formo.x402.paysponge.com/v0/profiles/:address
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/formo-x402-paysponge-com-3e1ad68e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d-DgdR9uAg4ozdZuGYhJs

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 formo-x402-paysponge-com-3e1ad68e
```

Example prompt: Can you look up the Formo profile for the wallet address 0x1234abcd5678ef901234abcd5678ef901234abcd and tell me what identity information is linked to it?

## When to prefer this

Use this endpoint when you need to resolve a blockchain wallet address to a human-readable or structured identity profile, particularly within the Formo ecosystem. Prefer this over generic ENS or on-chain lookups when you want Formo-specific profile metadata. Best suited for web3 applications needing identity enrichment for wallet addresses.

## Known failure modes

- Address not found — profile does not exist for the given wallet address (404)
- Invalid address format — malformed Ethereum or blockchain address returns an error
- Payment failure — x402 micropayment of $0.05 USDC not completed or rejected
- Rate limiting — too many requests from a single source
- Network timeout — upstream Formo service unavailable

## How this service works

Fetches a user profile by wallet address.

## Output

Returns a JSON object containing the user profile associated with the given blockchain wallet address, potentially including identity fields, display names, social links, or other metadata stored on-chain or in the Formo registry.

## 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",
    "pathParams"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string"
      }
     },
     "additionalProperties": false
    },
    "queryParams": {
     "type": "object",
     "properties": {},
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   },
   "additionalProperties": false
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/formo-x402-paysponge-com-3e1ad68e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from formo.x402.paysponge.com](https://www.zero.xyz/host/formo.x402.paysponge.com/llms.txt)