How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

anew Write/Read API

REST/HTTP API to encode self-contained HTML into shareable URLs (POST /write) and read pages back (GET /{slug}), with OpenAPI 3.1.1 contract. Unauthenticated and free.

This API exposes 4 operations across 4 paths, organized into 3 resource areas, and defines 4 schemas. It is described by OpenAPI 3.1.1, at version 1.0.0.

Requests are made against a single base URL, https://anew.page.

4 operations 4 paths 4 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
1.0.0
Base URL
https://anew.page
License
ISC
Resource Areas
3

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. They span 3 resource areas: pages, mcp, a2a. Each is listed below with its method, path, parameters, and response codes.

pages 2

Write self-contained HTML pages, and read them back.

POST
/write
Write HTML to an anew.page URL
writePage 1 param body → 200400405413429
GET
/{slug}
Read a page
readPage 2 params → 200404451502
mcp 1

Model Context Protocol JSON-RPC endpoint.

POST
/mcp
MCP JSON-RPC endpoint
mcpRpc 3 params body → 200202400403404405413429
a2a 1

Agent2Agent (A2A) protocol JSON-RPC endpoint.

POST
/a2a/v1
A2A JSON-RPC endpoint
a2aRpc 1 param body → 200400405413429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are WriteResult (6 properties), JsonRpcResponse (4 properties), JsonRpcError (3 properties), Error (1 property). Each schema is shown below with its type and property counts.

Error
object
The envelope every REST failure answers with: a machine-readable code, a human-readable message, a hint where one helps, details where there is a measurement.
1 property 1 required
WriteResult
object
A successful write, for callers that asked for application/json instead of the bare URL. The same numbers the Anew- response headers carry.
6 properties 5 required
JsonRpcError
object
A JSON-RPC 2.0 error response: parse error -32700, invalid request -32600, method not found -32601, invalid params -32602, header mismatch -32020, unsupported…
3 properties 2 required
JsonRpcResponse
object
A JSON-RPC 2.0 response: exactly one of result or error is present.
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anew-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of anew Write/Read API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.