# Bluesky Actor Profile Lookup (x402)

> Bluesky Actor Profile Lookup (x402) is a paid API for AI agents from api.naco.li, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Fetches a Bluesky user's public profile metadata including follower/following counts, post count, bio, and handle.

## Facts

- Endpoint: POST https://api.naco.li/v1/getActor
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bluesky-actor-profile-lookup-x402-0976a2ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cw-JFdPSAmuNGswTOUqHo

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 bluesky-actor-profile-lookup-x402-0976a2ad -d '<json body>'
```

Example prompt: Can you pull up the Bluesky profile for the user handle 'bsky.social' — I want to see their follower count, post count, and bio?

## When to prefer this

Use this endpoint when you need structured Bluesky-specific profile metadata for a known handle, especially in autonomous agent workflows where micropayment-based access (x402/USDC) is already set up. Prefer this over scraping or the native AT Protocol API when you want a clean REST interface with a predictable schema.

## Known failure modes

- Author handle not found — returns error or empty actor
- Invalid or malformed handle format — request validation failure
- Bluesky API unavailable — upstream timeout or 5xx error
- Payment failure via x402 — 402 response if USDC payment not processed

## How this service works

Auto-generated REST API matching active Model Context Protocol (MCP) tools.

## Output

Returns a structured actor object containing the user's Bluesky platform name, handle, follower count, following count, post count, and optionally their display name, bio, avatar URL, and profile URL.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "author"
 ],
 "properties": {
  "author": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "actor"
 ],
 "properties": {
  "actor": {
   "type": "object",
   "required": [
    "platform",
    "handle",
    "followersCount",
    "followingCount",
    "postCount"
   ],
   "properties": {
    "bio": {
     "type": "string"
    },
    "url": {
     "type": "string"
    },
    "handle": {
     "type": "string"
    },
    "platform": {
     "type": "string"
    },
    "avatarUrl": {
     "type": "string"
    },
    "postCount": {
     "type": "integer"
    },
    "displayName": {
     "type": "string"
    },
    "followersCount": {
     "type": "integer"
    },
    "followingCount": {
     "type": "integer"
    }
   },
   "additionalProperties": false
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bluesky-actor-profile-lookup-x402-0976a2ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.naco.li](https://www.zero.xyz/host/api.naco.li/llms.txt)