The reader's API (fwetch.lol, gekker.lol, api.vulpinenetwork.com)

Generated from the source by docs/make-api.py; each description is the comment the code carries. Base URL: https://fwetch.lol/api. Reads are open; writes are signed records, sessions (x-fwetch-session) or raw transactions.

300 routes in 109 groups.

/activity

• GET /api/activity. Daily activity for the last N days, for charts.

/admin

• POST /api/admin/ads/settle. Preview or pay a settlement. Curators.
• POST /api/admin/banners. Curators: switch one on or off, delete it, or add a new one.
• POST /api/admin/boards. Curator dashboard: which boards are up front, in what order, and hidden.
• POST /api/admin/credits. A curator loads a balance by hand (a friend paid you in cash; testing).
• POST /api/admin/curate. Curators: hide or restore a post, a listing or a picture.
• POST /api/admin/featured. Curators: put a collection forward, or take it back.
• POST /api/admin/founders/settle. house in one transaction, published like everything else.
• POST /api/admin/house-ads. capped so nobody turns the ad table into a file host.
• POST /api/admin/house-ads/delete. Curators: remove one of the house's own adverts.
• POST /api/admin/house/split. Curators: split the house's fattest coin into many, so it can pay for several things at once.
• GET /api/admin/houses. and the time, so one capture cannot be replayed as another.
• POST /api/admin/houses. Add a house, switch one off, fund it from house 0 or sweep it back. Signed by the key that holds #0 or #1.
• POST /api/admin/portraits. Curators: choose the collection portraits come from.
• POST /api/admin/portraits/backfill. Curators: draw portraits for numbers that have none.
• POST /api/admin/remint. same rules as the self-service re-mint.
• POST /api/admin/retire. is free to mint again. Curator only.
• GET /api/admin/status/:addr. Whether an address is a curator, and what it holds.
• POST /api/admin/welcome. Curators: choose the collection new members are given a fox from.
• POST /api/admin/welcome/backfill. Curators: give a welcome fox to members who joined before there was one.

/ads

• GET /api/ads. Every booking, for the dashboard. Advertisers see their own; curators see all of them.
• GET /api/ads/:txid/stats. How an advert has done: views and clicks.
• GET /api/ads/current/:slot. records arrives at the same answer.
• GET /api/ads/go/:txid. whether the ad worked. /api/ads/go/:txid records one and redirects.
• POST /api/ads/impression. lurkers without a session do not move money.
• GET /api/ads/rates. What an advert costs, and how the money is split.
• GET /api/ads/settlements. Published, so anyone can check the split against the transaction.

/apps

• GET /api/apps. Applications for the desktop, published on chain by anyone.

/arbiters

• GET /api/arbiters

/assertion

• GET /api/assertion/:txid. ---- Assertions: the primitive, readable directly ----

/assertions

• GET /api/assertions. Records filed as fwetch-assert, the protocol's escape hatch, by type, author or app.

/b

• GET /api/b/:hash. The bytes of an inscription by its hash: pictures, videos and files are served from here.

/babel

• POST /api/babel/gallery/locate. Where an image sits in the Library of Babel's gallery.
• POST /api/babel/locate. address in a browser, a reader and here.
• GET /api/babel/read/:coordinate. The text at a Library coordinate, which is where a Babel page's words actually live.
• GET /api/babel/shelf/:prefix. What else sits on this shelf: the "walk to the next page" query.

/balance

• GET /api/balance/:address. BSV balance for an address (confirmed + unconfirmed), in sats and BSV

/banners

• GET /api/banners. Every banner this reader has, by theme.
• GET /api/banners/random. One of a board's own banners, picked at random.

/board

• GET /api/board/:slug.glb. A board's coin as a 3D object.
• GET /api/board/:slug.png. The board coin's art: same generator as the number coins, board design.
• GET /api/board/:slug.svg. the board's picture is its deed now, not a coin

/boards

• GET /api/boards. Every board that is not hidden.
• GET /api/boards/:slug. One board: who holds it, its rules and its look.
• GET /api/boards/:slug/available. Gekker: is a board's tag free to buy, and for how much
• GET /api/boards/:slug/channels. most. Adding or removing one is signed by the owner's identity key.
• POST /api/boards/:slug/channels
• GET /api/boards/:slug/channels/:name/members
• POST /api/boards/:slug/channels/access. owner and the moderators. Signed by the owner's identity key.
• POST /api/boards/:slug/edit. The owner may rename and describe their board.
• POST /api/boards/:slug/flag. way a club is entered with a pin. The flag shows on posts like any other.
• POST /api/boards/:slug/flag/give. Give (or take back) the board's flag. Owner only.
• GET /api/boards/:slug/icon
• POST /api/boards/:slug/icon
• GET /api/boards/:slug/members. Who posts on a board, and who moderates it.
• POST /api/boards/:slug/moderate
• GET /api/boards/:slug/roles
• POST /api/boards/:slug/settings. Owner settings: private on/off, members in and out.
• POST /api/boards/buy. Buy a board: 1 BSV to #1, then the house mints the board coin to you. Curators skip the payment. A board that already has a coin is taken.

/broadcast

• POST /api/broadcast

/bsv

• GET /api/bsv/feed

/cache

• POST /api/cache. ---- Cache: bury a document, dig it up by name ----
• GET /api/cache/:name
• GET /api/cache/:name/plan
• GET /api/cache/:name/sats. wallet of ours, no card. Any wallet that can send.
• GET /api/cache/:name/versions. Every version of a cache, newest first.

/cache-checkout

• POST /api/cache-checkout. generator can see them.

/cache-plans

• GET /api/cache-plans. ---- Yipnote's plan: what is on offer, what a cache has left, subscribing, managing ----

/cache-portal

• POST /api/cache-portal. Opens Stripe's own customer portal for the cache's subscriber: changing a card, or cancelling. Wants the cache's write token.

/chat

• POST /api/chat/:room
• POST /api/chat/:room/edit. there, since the chain is not changed; this reader shows the edit.
• POST /api/chat/:room/hide. Hide a chat message: jannies, curators, the board's owner.
• GET /api/chat/:room/messages. Messages in a chat room, or a DM room the member is part of.
• POST /api/chat/:room/pin. Pin: the board owner, a curator, or (in a DM) either party. Pinning writes the message to chain — the one part of chat that should outlive us.
• POST /api/chat/:room/react
• POST /api/chat/block. Block and unblock. Registered before /chat/:room, which would otherwise take "block" for the name of a room.
• GET /api/chat/blocks. Who the signed-in member has blocked.
• GET /api/chat/dm/:who. Start a DM: resolve who, and hand back their identity key so the client can encrypt to it.
• GET /api/chat/file/:name
• GET /api/chat/rooms. The rooms you can see: every board room you may enter, and your DMs.
• GET /api/chat/stream
• POST /api/chat/upload

/chronovisor

• GET /api/chronovisor/address/:addr. an address as Chronovisor knows it: who it is (user number, name, handle, picture), and every record it signed or inscription it was given
• GET /api/chronovisor/block/:height. one block: every Vulpine record Chronovisor has from it
• GET /api/chronovisor/holdings/:addr. what an address and its account hold: BSV, tokens, ordinals, user numbers, land, boards (30 September 2026)
• GET /api/chronovisor/records. records, newest first; ?tag= ?author= to narrow, ?before=<id> to page back, ?after=<id> to catch up oldest first
• GET /api/chronovisor/search. one box for everything: a transaction id, an address, a block height, a #user number or a $handle
• GET /api/chronovisor/status
• GET /api/chronovisor/stream. new records as they arrive, for anyone following along: ?tags=fwetch-post,fwetch-chat, ?after=<id> to resume
• GET /api/chronovisor/tx/:txid
• GET /api/chronovisor/txinfo/:txid. went, and the records inside; the page at /chronovisor/tx/<txid> shows it

/classified

• GET /api/classified/:txid. One posting in full.

/classifieds

• GET /api/classifieds. Cregs List postings, by category, place or search.

/coin

• GET /api/coin/:number.glb. A user number's coin as a 3D object.
• GET /api/coin/:number.png. A user number's coin as a picture.
• GET /api/coin/:number/inscribe. base64 payloads the client inscribes on-chain when minting a Fwonk

/coins

• GET /api/coins/status/:addr. duplicates need to see this too.
• GET /api/coins/verdicts. For each outpoint: whether it really is the number it claims, an old design, or a duplicate. Ask this before offering to send or burn a coin.

/collections

• GET /api/collections. Collections the reader knows, or one creator's.
• POST /api/collections. Create. Signed by the creator; stays a draft until published.
• GET /api/collections/:id. One collection and the pieces in it.
• GET /api/collections/:id/can-mint. no money has moved.
• POST /api/collections/:id/delete. delete too (spam). The images go with it.
• POST /api/collections/:id/mint. market fee, which covers the inscription.
• GET /api/collections/:id/preview. the browser; the server composites on every call, so it is rate limited.
• POST /api/collections/:id/publish. Publish: freeze the layers, open the mint. Every variant must be uploaded.
• POST /api/collections/:id/variant. Upload one variant image. PNG, same size as the collection, one call each. Signed by the creator. Drafts only.

/content

• GET /api/content/:outpoint

/credits

• GET /api/credits/:addr. A member's credit balance with the house.

/debug

• GET /api/debug/identity/:addr. Diagnostic: exactly what the index holds for one wallet. Built because "the profile does not show" kept being guessed at instead of observed.

/deed

• GET /api/deed/board/:slug.svg. A board's deed, drawn.
• GET /api/deed/land/:parcel.svg. as SVG so a wallet renders them on a 3D card.

/delegates

• POST /api/delegates. Let another key post as your number, or take that back.
• GET /api/delegates/:number. cannot transfer the coin, change the profile, or delegate onward.
• GET /api/delegates/for/:addr. Which numbers may this address post as? Its own, plus every delegation.

/donate

• GET /api/donate. Giving the network money on purpose. Everything here has been somebody paying for a thing: a name, a board, a listing, a year of Yipnote. There was no way to simply put money in, which is the one thing people do for something they like. It goes to the house, which is what pays for everybody's minting, profiles and posts, so a donation is not a tip to a person: it buys somebody else's first records

/economic

• GET /api/economic. about anybody.
• GET /api/economic/:who. One person: their frens, what each holds, and the total. Named by number or address.
• GET /api/economic/:who/addresses. network has never been told about.

/escrow

• GET /api/escrow/:order
• POST /api/escrow/:order/sign
• GET /api/escrow/disputes. the arbiter's queue (1 October 2026): every order paid into escrow that is disputed and not yet released or refunded, oldest first, with who has signed what so far

/featured

• GET /api/featured. The collections this reader puts forward, which is what the Library and the profile picker show.
• GET /api/featured/mine/:addr. directly, which is the only place ownership of a piece is actually tracked.

/feed

• GET /api/feed. ---- FEED ---- feed with a small peek of replies under each post

/fireworks

• GET /api/fireworks. SINGLE-SIG (no 2-of-2 co-signature), so the owner alone can move it. Diagnostics: what version is actually running, and what does the index hold? Useful for telling "the fix is not deployed" apart from "the fix did not work". Fox Fireworks (1 October 2026): where its 2-sats-a-note payout goes, and how many shots the chain has seen under the Vulpine blast tag.

/flags

• GET /api/flags. Every flag that can be earned or awarded.
• GET /api/flags/:addr. because where somebody was when they posted is not a fact about who they are.
• POST /api/flags/award. Award or revoke. Curators only, checked against who actually holds #1 or #2 rather than anything the caller claims.
• POST /api/flags/define. Curators: add a flag or change how it is awarded.
• POST /api/flags/delete. Curators: remove a flag.
• GET /api/flags/images. Create or change a flag, and set the rule that awards it. Curators only. The pictures a flag can be. Just what is in the folder, so adding a flag design is dropping a 50x35 PNG into public/flags/.
• POST /api/flags/run. Run every automatic rule now. Also runs on its own schedule; this is for a curator who has just written a rule and wants to see it take effect.

/founders

• GET /api/founders/settlements. What the protocol has paid out to the founders, and when.

/foxcannon

• GET /api/foxcannon. SINGLE-SIG (no 2-of-2 co-signature), so the owner alone can move it. Diagnostics: what version is actually running, and what does the index hold? Useful for telling "the fix is not deployed" apart from "the fix did not work". Fox Fireworks (1 October 2026): where its 2-sats-a-note payout goes, and how many shots the chain has seen under the Vulpine blast tag.

/frens

• GET /api/frens/:who. is the protocol's, not Post Economic's.
• GET /api/frens/:who/with/:other. Is this pair frens, and which way round? For a button that has to know what it says before anybody presses it.

/frontpin

• POST /api/frontpin
• GET /api/frontpin/price. Pin a thread to the front page: free for the founders' seats and curators, $5 an hour for anyone else, paid to the house like a board.

/gekker

• GET /api/gekker/joined. always the ones you own or are a member of. Kept by your session.
• POST /api/gekker/joined
• POST /api/gekker/keys. the owner hands out a channel's key: envelopes for one epoch, signed
• GET /api/gekker/keys/:room. your envelopes for a room, by every address linked to your session
• GET /api/gekker/pubkey/:addr. an address's identity key, which envelopes are sealed to: its own, or that of the identity linked to it
• GET /api/gekker/who/:addr. address linked to them. Public, and cached for a minute.

/handle

• GET /api/handle/:number. Who holds a user number, and the coin that carries it.

/handles

• GET /api/handles/can-mint/:address. Whether this address may mint a user number, and which number is next.
• POST /api/handles/claim-mint. out.
• POST /api/handles/claim-mint/done. The mint went through (or did not). Either finish the claim or drop it.
• GET /api/handles/next. ---- HANDLES ----
• GET /api/handles/recent. The newest members, for the front page.
• GET /api/handles/taken/:number. is a specific handle number already minted? (uniqueness guard before mint)

/health

• GET /api/health. 200 when this box is well, 503 with the reason when it is not. ?format=text answers HEALTHY or UNHEALTHY on the first line, for a monitoring service to watch.

/house-ads

• GET /api/house-ads. the same gate as everything else on the ads page.

/id

• GET /api/id/:addr.svg. the ID card: who a key is on the network, drawn live

/index

• POST /api/index/:txid. ---- index a specific txid on demand (e.g. a post signed via wallet extension that we didn't broadcast ourselves) ----

/indexer

• GET /api/indexer/status. Whether the indexer is running, when each loop last beat, how stale each kind of item is, and why it is not running if it is not.

/launch

• GET /api/launch/:id. one launch, by its record's txid or its token id
• GET /api/launch/:id/holders. a launch coin's holders, from what each buyer bought off its ladder (the rich list)

/launches

• GET /api/launches

/legacy

• POST /api/legacy/scan/:addr. Runs in the background; poll /legacy/status/:addr for progress.
• GET /api/legacy/status/:addr. What an old Twetch or Twonk address still holds here.

/link

• POST /api/link. for something the app can observe on its own the moment you connect.

/lock

• GET /api/lock/:outpoint. ---- WRITE: broadcast a client-signed tx, then index it immediately ---- a listing's lock, read for a page about to buy it or take it back (v1 or v2)

/mail

• GET /api/mail/lookup/:local. same key.

/market

• GET /api/market. The market: listings by kind, category, seller, shop or tag.
• POST /api/market/checkout. Checkout in dollars: a Stripe Checkout session with the split and a held charge. The order record is written when Stripe says it is paid.
• GET /api/market/coin/:number. everything about one number: who owns it, is it for sale, what has it sold for
• GET /api/market/dropped. and used to keep it to itself.
• GET /api/market/fee. The network's cut of a sale.
• GET /api/market/listing/:txid. One listing in full.
• GET /api/market/listings
• GET /api/market/mine/:address. what the connected wallet owns and could sell
• POST /api/market/offer. to come back, so that lost the sale outright.
• GET /api/market/offer/:outpoint. One offer made on a listing.
• GET /api/market/order/:txid
• GET /api/market/orders/:addr. A member's orders, bought and sold.
• GET /api/market/quote/:txid. is needed for the script.
• GET /api/market/sales. What has sold lately.
• GET /api/market/seller/:addr. A seller: what they have sold and what people said.
• GET /api/market/shop/:txid
• GET /api/market/shops/of/:addr. A shop and everything in it. a seller's own shop, the latest they opened (29 September 2026: the wallet could not find it)
• POST /api/market/stripe/onboard. Seller onboarding: one Stripe-hosted page. We keep only the account id.
• GET /api/market/stripe/status/:addr. Whether a seller can take card payments yet.

/maze

• GET /api/maze/board
• POST /api/maze/run. and nothing here costs money or records any.
• GET /api/maze/skulls. every player's last fall, newest first, for the maze to lay their skulls
• POST /api/maze/treasure
• GET /api/maze/treasures. the Treasure Room: every treasure found, newest first, public

/mcp

• GET /api/mcp/:name. Some clients look before they leap.
• POST /api/mcp/:name. whoever added them and the model never names a cache itself.

/members

• GET /api/members. Everyone. The same query the sidebar's New members uses, uncapped.
• GET /api/members/new. Newest members, for the leaderboard on the right rail.

/meme

• GET /api/meme/:txid. One entry, with everything known about it: who made it, who put it on chain, and how many times it has been inscribed since.

/memes

• GET /api/memes. are all matched.
• GET /api/memes/bulk. dozen round trips on every render. One call, cached by the client.
• GET /api/memes/claimed/:txid/:addr. Has this member already claimed an edition of this meme? One each.
• POST /api/memes/discover. point of an open protocol.
• GET /api/memes/dupes. entry itself and leave the duplicates as the only copies.
• GET /api/memes/held/:addr. the same answer ownership enforcement gives.
• GET /api/memes/may-post/:txid/:addr. May this address post that meme? Asked by the composer before the post is signed, so nobody pays for a post whose meme will be stripped on arrival.
• GET /api/memes/sha/:sha. them. Answers with the entry so the composer can offer to post it.
• GET /api/memes/shelves. The Memetic Library's shelves.
• GET /api/memes/tags. The shelves and tags that actually exist, so browsing does not depend on guessing what someone might have typed.

/mint

• GET /api/mint/estimate. mint-cost estimate for the composer

/mod

• GET /api/mod/am-i/:addr. ---- Jannies ----
• GET /api/mod/hidden. What is hidden right now, and the log. For the janny desk.
• POST /api/mod/hide. Hide or restore a post or a meme. The record stays; it stops being served. Logged with who and why, so curators can review what their jannies do.
• POST /api/mod/sticky. Sticky a thread to the top of its board. The board's owner, or a curator.

/name

• GET /api/name/:name. ---- $handles ----
• GET /api/name/resolve/:name. ---- Naming: .fox ---- name.resolve is the one every reader and the gateway calls.

/names

• GET /api/names. Every .fox name the indexer knows and where each points.
• GET /api/names/for/:addr. The .fox names and handles an address holds.
• GET /api/names/owned/:addr. name.list_owned — what this wallet holds, for the wallet's own panel.
• POST /api/names/reindex. mempool poll missed while WoC was throttling. Index whatever is not known.

/network

• GET /api/network. The network in one call, for the protocol's home page and anyone else.
• GET /api/network/stats. How many members, records, boards and names the network has.

/notifications

• GET /api/notifications/:addr. address and a coin sent to another are both theirs.

/owned

• GET /api/owned/:address. page load must be cheap and unlimited; the mint check keeps its limit.

/pay

• POST /api/pay/checkout. Stripe Checkout: a card payment becomes sats on the member's balance. Needs STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET and FWETCH_SATS_PER_USD.
• POST /api/pay/webhook. Stripe tells the reader a card payment for credits went through.

/people

• GET /api/people. Find people as you type: a number, or the start of a name or $handle. It returns only what chat already shows publicly: name, number and picture.

/piece

• GET /api/piece/:txid. One piece, by the txid of its inscription: what the profile click shows.

/pieces

• POST /api/pieces/verdicts. 'unknown' and kept.

/poll

• GET /api/poll/:txid. One poll: its question, its answers and the count so far.
• GET /api/poll/:txid.csv. CSV for the spreadsheet people.
• POST /api/poll/:txid/ballot. An encrypted ballot arrives unsigned by any identity — that is the point. The house verifies it exactly as the indexer will, then writes it.
• GET /api/poll/:txid/encrypted. A sealed poll's published hashes, before the reveal.
• POST /api/poll/:txid/token. A token for voting in a sealed poll, so a vote can be counted without being read.
• GET /api/poll/:txid/verify. Verify one sealed vote yourself: does sha256(choice:salt) match the commitment on chain?

/polls

• GET /api/polls. Open polls, newest first.
• POST /api/polls/ceremony. Before posting an encrypted poll: get a ceremony. The public parts go in the post; the private parts stay here against the poll's txid once known.
• POST /api/polls/ceremony/bind. Once the poll post exists, bind its ceremony to the txid.

/portraits

• GET /api/portraits. How many portraits are ready for the numbers that have been minted.
• GET /api/portraits/:number. The portrait that belongs to a user number.

/post

• GET /api/post/:txid. One post by its txid, with its author, flag and counts.

/post-no

• GET /api/post-no/:board/:no. >>412 on /K/ — which post is that? For quote-links.

/posts-by

• GET /api/posts-by/:addr. posts by wallet address — identity is the ADDRESS, not the number

/presence

• GET /api/presence/:room. Who else is in that room right now. Never signed, so never proof of anything.
• POST /api/presence/:room. Say where you are standing in Tartary. Kept in memory for twenty seconds and never written to the chain.

/profile

• GET /api/profile/:handle. ---- PROFILES ----

/profile-addr

• GET /api/profile-addr/:addr. profile by address — always resolvable, even before a handle exists. Returns both addresses so the client knows which one to ask about tokens.

/project

• POST /api/project
• GET /api/project/:project
• GET /api/project/:project/briefing
• GET /api/project/:project/skill/:skill
• POST /api/project/:project/update

/rate

• GET /api/rate. What a satoshi is worth in dollars right now, so a price can be shown in either.

/rawtx

• GET /api/rawtx/:txid. Raw hex for a transaction, used to build the inputBEEF a wallet needs before it will accept an input for an output it does not manage itself.

/reconcile

• POST /api/reconcile. Force a reconciliation. Useful after a transfer made elsewhere, and for telling "the index is behind" apart from "something is wrong".

/replies-by

• GET /api/replies-by/:addr. replies written by this member, with the text they were replying to

/resolve

• GET /api/resolve/:handle. ---- IDENTITY: resolve a Twetch user number to an address (bootstrap) ----
• GET /api/resolve/:who

/richlist

• GET /api/richlist/:kind

/session

• POST /api/session. signs one request, gets a token, and sends the token with reads.

/sigil

• GET /api/sigil/:txid. full sigil metadata for one txid (incl. glbModel for 3D) — the unspent listing is lightweight; this fetches the rich per-inscription data on demand

/snapshot

• GET /api/snapshot. Set FWETCH_SNAPSHOT_KEY to turn it on; the key is the only gate.

/sponsor

• POST /api/sponsor/anon. post carries anon:1 and no key; it renders as any other anonymous post.
• POST /api/sponsor/bsv. Replies and likes to other BSV apps' posts, paid by the house (30 September 2026): Vulpine first, then Bitcoin Schema's B, MAP (app vulpine) and the member's own AIP signature.
• POST /api/sponsor/claim-for. and still stop at the supply. Rate-limited per IP.
• POST /api/sponsor/inscribe
• POST /api/sponsor/mint. only the member can ask for their own coin.
• POST /api/sponsor/opreturn
• GET /api/sponsor/status. What the house holds, its coin pool, and what it has spent today.
• POST /api/sponsor/transfer/finish. The member's signed transfer, broadcast and paid for by the house.
• POST /api/sponsor/transfer/prepare. The house builds a transfer of an ordinal the member owns, for the member to sign.
• POST /api/sponsor/upload. A picture on chain, for listings and shops: signed request, bytes as a data URL, the house writes a B file and returns its reference.

/stream

• GET /api/stream. and the ordinary routes answer for it.

/tartary

• GET /api/tartary/deed/:parcel. is today's. Open to every site; docs/DEEDS.md, served at /deeds.
• GET /api/tartary/deeds. whether somebody is sweeping.
• GET /api/tartary/deeds/all. Every founded deed, a page at a time, for a game that wants the whole land at once: ?after= the last seq you were given, ?limit= up to 1000.
• GET /api/tartary/derivation. The derivation itself, published: the constants a renderer must match.
• GET /api/tartary/district/:height. district.info — everything about one district, derived.
• GET /api/tartary/founded-map. ?addr= the count of the caller's own (their linked addresses included).
• GET /api/tartary/founded/:addr
• GET /api/tartary/map. response says how many are still coming, so a renderer can ask again.
• POST /api/tartary/messages. parcel.enumerate — the parcels a district actually contains. What this host knows about a handful of transactions. A district's corridors are its transactions, and a corridor with something written in it is worth walking down. Fetching every transaction to look for an OP_RETURN would be thousands of requests for one room, so this asks a cheaper question: of these txids, which ones are records this
• GET /api/tartary/parcel/:id. parcel.owner, plus what stands on it and any live lease.
• GET /api/tartary/parcels/:height. The parcels in one district, read from the block itself.

/tip

• GET /api/tip/quote/:post. Tipping a post: exactly what to pay, to whom.

/tips

• GET /api/tips/:post. Who has tipped a post, and how much.

/tod

• GET /api/tod/:name. One tod by the name it claimed, with the inscription to install from.

/tods

• GET /api/tods. The Den: every tod the indexer has seen, newest first. ?q= searches.

/tokens

• GET /api/tokens/:id/chart

/tx

• GET /api/tx/:txid. raw transaction passthrough, used when signing a listing

/tx-exists

• GET /api/tx-exists/:txid. does this txid exist on the network yet? (for honest "posted" confirmation)

/utxos

• GET /api/utxos/:address. ---- UTXOs for the client to build a tx ----

/verified

• POST /api/verified. For a list of outpoints, whether each is what it claims to be.

/version

• GET /api/version

/wallet

• GET /api/wallet/:address. Everything an address holds: numbers, pictures, names, deeds and tods. ?fresh=1 skips the kept answer.
• POST /api/wallet/warm. Ask the reader to look up an address before it is needed, so the wallet view opens at once.

/welcome

• GET /api/welcome. clear it. See lib/portraits.js. Welcome foxes: a piece from the house's pocket to every new member. See lib/welcome.js.

/whereami

• GET /api/whereami. Where the caller appears to be, so the client can show a flag without the member telling us anything. Country level, and it fails silently.
• GET /api/whereami/debug. address, which they already know.

/wiki

• GET /api/wiki. asked about. A dead loop was invisible until something looked wrong. The whole encyclopedia, in one answer. Babel is meant to be read by programs as much as by people: the corpus is already signed, timestamped and public, and a thing that wants to learn from it should not have to walk a thousand addresses to do so. This hands over every page's current version, with what each one links to, in pages
• GET /api/wiki/:subject. A Babel page: its current version, its timeline and what it links to.
• GET /api/wiki/edges/:subject. snapshot.query — the graph as it stood at a moment.
• GET /api/wiki/frontier. Pages other pages link to that nobody has written yet.
• GET /api/wiki/snapshot/:ts. The frontier: subjects an edge points at that have no article yet. Visible gaps are the point — they are where the graph funds its own construction.
• GET /api/wiki/version/:txid. descent graph between subjects. One version of a page, by its record: what the timeline reads to show an old version's text (its coordinate is the text).