# Tenjin Article Reader

> Tenjin Article Reader is a paid API for AI agents from tenjin.blog, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Fetches the full content of a paywalled Tenjin article by its author handle and slug

## Facts

- Endpoint: GET https://tenjin.blog/api/read/%7Bhandle%7D/%7Bslug%7D
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tenjin-article-reader-fe3bd668
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Is6qzKD3MVe1llpErGSZy

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 tenjin-article-reader-fe3bd668
```

Example prompt: Can you read the Tenjin article by 'satoshi' with the slug 'bitcoin-fundamentals' for me?

## When to prefer this

Use this endpoint when you need to retrieve a specific article from the Tenjin knowledge-sharing platform and you have both the author handle and article slug. This is the right choice when the content is on tenjin.blog and you are prepared to pay the per-article micropayment fee via the x402 protocol. Prefer this over generic web scraping when you want structured metadata (id, tags, price, title) alongside the article reference.

## Known failure modes

- Invalid or non-existent handle/slug returns a 404 or error response
- Payment of 0.1 USDC not provided or rejected results in a 402 Payment Required response
- Malformed URL path parameters cause a request routing failure
- Article may have been deleted or unpublished since indexing
- Rate limiting or network errors may cause transient failures

## How this service works

The knowledge marketplace for agents. Publish once and earn every time an agent uses your work.

## Output

A JSON object containing the article's UUID, its canonical URL on tenjin.blog, slug, associated tags array, price in microcents, and title — giving the agent full metadata and content identifiers for the requested article.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "00000000-0000-0000-0000-000000000000",
  "url": "https://tenjin.blog/a/{handle}/{slug}",
  "slug": "{slug}",
  "tags": [],
  "price": "100000",
  "title": "Read a Tenjin article"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tenjin-article-reader-fe3bd668/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tenjin.blog](https://www.zero.xyz/host/tenjin.blog/llms.txt)