The data and the API.

Base https://brich.house/api/v1. Every call carries Authorization: Bearer <key>. Every answer is JSON and opens with two fields: licence, the line below, and as_of, the date the data was last read or signed (not the time of the call). Errors answer the same way, with error and message. GET only; the API writes nothing.

1. GET /api/v1/weeks

   Every week on record, newest first: the week's Monday, its window, the read dates, the signed date, the platforms measured and where its files are.

2. GET /api/v1/weeks/{date}

   One week's public JSON, exactly as the week file is written: every platform's thirteen measures with their marks and intervals, the totals, what was not measured and why, the endpoints read.

3. GET /api/v1/platforms/{slug}

   One platform's current page data: chain or off chain, custodian as its pages state it, readability grade with its reason, the latest week's figures, the "Where your $100 sits" rows with their dates and cites, the Platform Record terms entries, the newest legal log entries naming it.

4. GET /api/v1/platforms/{slug}/historywith a paid plan

   The platform's columns in every week on record and every dated reading of its terms entries. Available with a paid plan; until then the route answers 402 and says so.

5. GET /api/v1/legal-log

   The dated regulatory, court, network and platform-rule entries, newest document first. Narrow with ?platform= (its name; entries marked "all" come too), ?topic= (regulator, court, network, platform rule) and ?since= (a document date, YYYY-MM-DD or YYYY-MM).

The limit

60 calls a minute per key, counted as a bucket that holds 60 and refills one a second. Past it the answer is 429 with Retry-After in seconds. Every authenticated call is counted on the key, and the account page shows the count and the date of last use.

The limit’s edge

The bucket lives in the memory of the server instance that answered, and more than one instance may answer at once, each with its own bucket. Calls spread across instances can pass 60 in a minute in total. The limit is a fuse against a tight loop; the count on the key is the record.

Status codes

200 the answer. 400 a filter that is not a date. 401 no key, a key not recognised, or a revoked key. 402 the history route without a paid plan. 404 a week or a platform not on record. 429 past the limit. 500 our side; write to hello@brich.house.

What is never in an answer

A wallet address, a cert number, a person. The routes carry the platforms’ public records and the log of public documents, as the pages do, and nothing else.