# TON Fragment Search API (x402)

> TON Fragment Search API (x402) is a paid API for AI agents from x402-crypto.vercel.app, paid per call via x402, $0.052126/call, status unknown (last checked 2026-09-15).

Searches TON Fragment marketplace items using a paid micropayment-gated API endpoint

## Facts

- Endpoint: POST https://x402-crypto.vercel.app/api/ton-fragment/%7Bpath%7D
- Price: $0.052126/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ton-fragment-search-api-x402-a1a63a26
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EEYarRvxk9ZZ2f3YS6WR2

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 ton-fragment-search-api-x402-a1a63a26 -d '<json body>'
```

Example prompt: Search TON Fragment for Telegram usernames matching 'crypto' and show me what listings come up.

## When to prefer this

Use this endpoint when you need programmatic access to TON Fragment marketplace search results, particularly for discovering Telegram usernames, anonymous numbers, TON domains, or NFT gifts listed on Fragment. Prefer this over scraping Fragment directly or manual search when you need automated, agent-driven lookups with pay-per-query micropayment pricing via x402.

## Known failure modes

- Invalid or empty query string returns an error or empty results
- x402 payment failure results in 402 Payment Required response
- TON Fragment upstream API downtime causes 502/503 errors
- Malformed path parameter leads to 404 not found
- Rate limiting or payment processing delays may cause timeouts

## How this service works

Paid cryptocurrency API endpoints via x402 micropayments

## Output

Returns a JSON object with a 'data' field containing the upstream Fragment API response, which includes matching marketplace listings, item details, prices, and availability for the searched query. The exact structure of the nested data object may vary.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "Search query for TON Fragment items"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Response payload from the upstream API (structure varies by endpoint)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ton-fragment-search-api-x402-a1a63a26/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-crypto.vercel.app](https://www.zero.xyz/host/x402-crypto.vercel.app/llms.txt)