# SEO Backlink Check API (x402 USDC)

> SEO Backlink Check API (x402 USDC) is a paid API for AI agents from seo-mcp-x402.abacusai.app, paid per call via x402, $0.03/call, status unknown (last checked 2026-11-16).

Returns backlink profile data for a domain, including referring domains, trust score estimate, and domain authority estimate, for 0.03 USDC per call.

## Facts

- Endpoint: POST https://seo-mcp-x402.abacusai.app/tools/backlink_check?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/seo-backlink-check-api-x402-usdc-e9637636
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EVom33NrSHBCpBgAV5LwQ

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 seo-backlink-check-api-x402-usdc-e9637636 -d '<json body>'
```

Example prompt: Can you check the backlink profile for example.com — I want to see how many referring domains it has and what its trust score and domain authority look like?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call backlink and domain authority snapshot without committing to a subscription-based SEO platform. It is ideal for agents that need on-demand domain vetting, competitor analysis, or pre-purchase domain evaluation using x402 micropayments on Base.

## Known failure modes

- 402 Payment Required if no valid x402 USDC payment is included — returns X-Payment header with payment details
- 400 Bad Request if domain input is missing or malformed after a valid payment has been made
- 503 or degraded results if upstream SEO data sources are unavailable
- Empty or low-confidence results for very new or obscure domains with minimal backlink history

## How this service works

Paid SEO tools and the **Token Security & Verdict API** (`POST /verdict`, 0.02 USDC), exposed both as REST
endpoints and as an **MCP server** (`POST /mcp`, Streamable HTTP).

### Token Security & Verdict API
`POST /verdict` with `{"address": "0x...", "chain": "base" | "ethereum"}` returns a risk score (0-100), flags,
liquidity, holder concentration, honeypot indicators, top holders and a short summary. Data: GoPlus Security,
DexScreener and public JSON-RPC; if every source is down the result is an estimate marked `"source": "estimated"`.
Payments go to `0x4C5D82B27E857E4FCE5607b34041aD2d9c74eD1B`; its EIP-712 domain name is **"Token Verdict x402"** (all other domain fields are as below).
Every unpaid GET/HEAD/POST returns 402 with
`X-Payment: {"amount":"0.02","currency":"USDC","recipient":"0x4C5D82B27E857E4FCE5607b34041aD2d9c74eD1B","network":"base","mimeType":"application/json","resource":"token_verdict"}`.
Invalid input after a valid payment returns **400** and the payment proof is not consumed.

### Standard x402 payments (recommended - settled on-chain, indexed by x402scan)
Every 402 carries a base64 `PAYMENT-REQUIRED` header (x402 v2): scheme `exact`, network `eip155:8453`,
asset USDC `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`. Retry with a `PAYMENT-SIGNATURE` header (v2 PaymentPayload, EIP-3009
`transferWithAuthorization`; v1 payloads in `X-PAYMENT` are also accepted). The server verifies via the PayAI facilitator,
runs the tool, then settles on-chain (facilitator pays gas) and returns the receipt in `PAYMENT-RESPONSE`.
Tool errors (e.g. 400 bad input) are **not** settled. Works out of the box with `@x402/fetch` + `@x402/evm`.

### Legacy payment flow (custom tx_hash proof)
1. Call a tool without payment -> **HTTP 402**. The `X-Payment` response header contains JSON:
   `{"amount","currency":"USDC","recipient","network":"base","mimeType","resource"}`.
2. Pay `amount` USDC on Base to `recipient`, then sign the EIP-712 typed data below with the payer wallet.
3. Retry with header `X-PAYMENT: {"tx_hash":"0x..","payer":"0x..","amount":"0.01","signature":"0x.."}`
   (raw JSON or base64 JSON) -> **HTTP 200** with results and an `X-Payment-Response` receipt header.

EIP-712 domain: `{name: "SEO MCP x402", version: "1", chainId: 8453, verifyingContract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913}`;
type `Payment(address payer, address recipient, uint256 amount, bytes32 txHash)` with `amount` in USDC atomic units (6 decimals).
Each `tx_hash` can be redeemed once. Rate limit: 10 calls / 60s per payer (HTTP 429).
If a tool fails (4xx/5xx tool_error) the payment is **not** consumed and can be retried.

## Output

A JSON object containing the queried domain, a list of referring domain hostnames, a count of referring domains, a trust score estimate (0-100), and a domain authority estimate (0-100), along with payment metadata including the payer address, amount, transaction hash, currency, and response time.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "minLength": 1,
   "description": "Bare domain, e.g. example.com"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "backlink_check",
  "result": {
   "domain": "example.com",
   "referring_domains": [
    "wikipedia.org"
   ],
   "trust_score_estimate": 85,
   "referring_domains_count": 3,
   "domain_authority_estimate": 90
  },
  "payment": {
   "payer": "0x0000000000000000000000000000000000000001",
   "amount": "0.03",
   "tx_hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
   "currency": "USDC",
   "response_time_ms": 850
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/seo-backlink-check-api-x402-usdc-e9637636/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from seo-mcp-x402.abacusai.app](https://www.zero.xyz/host/seo-mcp-x402.abacusai.app/llms.txt)
