# Farcaster User Profile Lookup by FID, Username, or Address

> Farcaster User Profile Lookup by FID, Username, or Address is a paid API for AI agents from api.web3identity.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Retrieves a Farcaster user's profile data including FID, username, display name, and follower count given a FID, username, or connected wallet address

## Facts

- Endpoint: GET https://api.web3identity.com/api/farcaster/dwr
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-web3identity-com-3b17558d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vQ9tE0UD6OrUXDKaM6v32

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 api-web3identity-com-3b17558d
```

Example prompt: What's the Farcaster profile for the username 'dwr' — I want their FID, display name, and how many followers they have.

## When to prefer this

Use this endpoint when you need to resolve a Farcaster identity from any of the three lookup keys — FID, username, or connected wallet address — especially in Web3 contexts where you need to bridge on-chain addresses to Farcaster social profiles. Prefer over scraping Warpcast directly for reliable structured data.

## Known failure modes

- User not found for given FID, username, or address returns 404 or empty result
- Invalid or malformed address/FID returns 400 bad request
- Rate limiting or payment failure returns 402 or 429
- Farcaster API upstream unavailability causes 503 or timeout

## How this service works

Get Farcaster user profile by FID, username, or connected address

## Output

Returns a Farcaster user profile object containing the user's FID (numeric ID), username (handle), displayName, and follower count.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "username": "dwr"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "fid": {
       "type": "number"
      },
      "username": {
       "type": "string"
      },
      "followers": {
       "type": "number"
      },
      "displayName": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## More

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