# ForgeMesh Content Signals Lookup

> ForgeMesh Content Signals Lookup is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Checks whether a domain permits AI use of its content by fetching and parsing robots.txt Content-Signal / aipref declarations into structured JSON with plain-English interpretation.

## Facts

- Endpoint: POST https://x402.forgemesh.io/domain-content-signals
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-content-signals-lookup-2f2ba9d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jDO6b9M2PRbLIfoJ1enI5

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 forgemesh-content-signals-lookup-2f2ba9d0 -d '<json body>'
```

Example prompt: Before I scrape nytimes.com for my RAG pipeline, can you check whether that domain actually permits AI use of its content — look at the robots.txt and any Content-Signal or aipref declarations and tell me what's allowed?

## When to prefer this

Use this endpoint as a pre-crawl compliance gate before scraping, RAG ingestion, or dataset collection from any external domain. Prefer it when your agent needs to verify AI content permissions specifically (ai-input, ai-train, search signals) rather than just generic robot exclusion rules. Essential for pipelines that must respect the emerging web standard for AI content gating, especially ahead of the September 2026 Cloudflare default changes.

## Known failure modes

- Domain is unreachable or does not exist — returns error or empty policy
- robots.txt is absent — interpretation defaults to permissive with note
- Malformed robots.txt with no parseable Content-Signal blocks — returns empty directives
- Network timeout fetching the remote robots.txt
- Domain string is malformed or missing — returns validation error

## How this service works

Content Signals lookup API: does this domain permit AI use of its content? Fetches robots.txt and parses Content-Signal / aipref declarations (search=, ai-input=, ai-train=) into structured JSON plus a plain-English interpretation, including related AI directives. The essential pre-crawl compliance check for scraping, RAG ingestion, and dataset agents as the web gates against bots (Cloudflare defaults change Sept 15, 2026). First mover — nobody else sells this check.

## Output

Returns structured JSON containing parsed Content-Signal and aipref directive values (search=, ai-input=, ai-train=) found in the domain's robots.txt, plus a plain-English interpretation of what AI uses are permitted or restricted, and any related AI-specific directives.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Domain to check, e.g. example.com"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "domain": "theverge.com",
  "signals": {
   "search": "yes",
   "ai-input": "no",
   "ai-train": "no"
  },
  "declared": true,
  "interpretation": "site declares: search=yes, ai-input=no, ai-train=no"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-content-signals-lookup-2f2ba9d0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)