# Proofivy Library Server – CryptoSlate Content Fetch

> Proofivy Library Server – CryptoSlate Content Fetch is a paid API for AI agents from library.proofivy.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches the full text of a CryptoSlate article and returns it with a cryptographic content ID (CID) commitment, billed per request via x402 micropayment.

## Facts

- Endpoint: POST https://library.proofivy.com/cryptoslate
- 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/proofivy-library-server-cryptoslate-content-fetch-5405736a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eBym6JQQibOQ5cDVb5shs

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 proofivy-library-server-cryptoslate-content-fetch-5405736a -d '<json body>'
```

Example prompt: Fetch the full text of that CryptoSlate article for me and give me the Proofivy CID so I can verify the content hasn't been tampered with.

## When to prefer this

Use this endpoint when you need the full text of a CryptoSlate article AND require a cryptographic guarantee (CID) that the bytes returned are authentic and unaltered. Prefer this over generic web scrapers or news APIs when content integrity verification is essential, such as for auditing, archiving, or downstream citation use cases, and when micropayment-per-request billing is acceptable.

## Known failure modes

- Payment fails or is insufficient — request rejected without content returned
- Invalid or unavailable article path — returns error status
- x402 payment protocol misconfiguration — payment not accepted
- Network timeout fetching source content — error or partial response
- CID generation failure — content returned but without integrity commitment

## How this service works

Cryptoslate content lookup. Include the content URL or slug in the request using the content_url key

## Output

A JSON object containing the full article text from CryptoSlate, a Proofivy cryptographic CID (e.g. bafkreiexample...) committing to the exact bytes returned, and a status field indicating success. The CID can be used to cryptographically verify the content was not altered.

## Example request

```json
{
 "content_url": "1-2-billion-just-left-bitcoin-etfs-3-ways-this-reset-could-flip-bullish-fast"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "content_url": {
   "type": "string",
   "description": "The URL or slug of the CryptoSlate article to retrieve"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "text": "The CryptoSlate article content...",
  "status": "success",
  "proofivy_cid": "bafkreiexample..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/proofivy-library-server-cryptoslate-content-fetch-5405736a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from library.proofivy.com](https://www.zero.xyz/host/library.proofivy.com/llms.txt)