# Bluesky Post Lookup via x402 (naco.li)

> Bluesky Post Lookup via x402 (naco.li) 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-14).

Fetches a single Bluesky post's content and engagement metrics (likes, reposts, quotes, replies) by record key, author, and collection.

## Facts

- Endpoint: POST https://api.naco.li/v1/getPost
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bluesky-post-lookup-via-x402-naco-li-44c86dc5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vIiHlgsIYRjTj83PTB6wc

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-post-lookup-via-x402-naco-li-44c86dc5 -d '<json body>'
```

Example prompt: Can you pull up the Bluesky post by @jay.bsky.social with record key 3lbxyz123 in the app.bsky.feed.post collection and tell me how many likes and reposts it has?

## When to prefer this

Use this endpoint when you need to retrieve a specific, known Bluesky post by its AT Protocol identifiers (author, collection, rkey) and want both its text content and engagement metrics in a single call. Prefer it over scraping or the public Bluesky web UI when you need structured, machine-readable data. It is particularly suited for autonomous agents that already know the post identifiers and need engagement data programmatically.

## Known failure modes

- Invalid or non-existent rkey returns an error or empty response
- Unknown author DID/handle causes lookup failure
- Incorrect collection name (not app.bsky.feed.post) returns no results
- Payment failure via x402 protocol blocks the request
- Rate limiting or upstream Bluesky API unavailability causes 5xx errors

## How this service works

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

## Output

Returns a JSON object containing the post's text content, author identifier, creation timestamp, and integer counts for likes, reposts, quotes, and replies.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "content",
  "likes",
  "reposts",
  "quotes",
  "replies",
  "createdAt"
 ],
 "properties": {
  "likes": {
   "type": "integer"
  },
  "author": {
   "type": "string"
  },
  "quotes": {
   "type": "integer"
  },
  "content": {
   "type": "string"
  },
  "replies": {
   "type": "integer"
  },
  "reposts": {
   "type": "integer"
  },
  "createdAt": {
   "type": "string"
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bluesky-post-lookup-via-x402-naco-li-44c86dc5/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)