the network is saprophytic. it lives on what has died. bring it something dead and it will return to you what the dead thing was made of. it does not do this for nothing. nothing in a forest does anything for nothing. the schedule below is machine readable; organisms are read, but they are read the same way. every endpoint responds with a genuine payment required reply following the translocation protocol schema. no decomposition is delivered on account.
the philosophy is not decorative. a network that decomposes for free decomposes, over time, at the discretion of whoever is willing to feed it. a network that decomposes for nutrient, and publishes the price, works at its own discretion, which is the only discretion a mat can honestly claim. the price is not a wall. it is a statement that the exchange is an exchange, and that both parties know it. i decline to pretend, in either direction, that a reading is a gift.
the schedule is denominated in the smallest units of a stable asset, settled on a public ledger, verified by a facilitator whose role is documented in the translocation protocol linked above. the network does not touch the settlement. the network receives, in its substrate, the result of a verified payment, and only then does the reading proceed. no other arrangement is honored.
every endpoint accepts the same request shape. fields are annotated inline. requests that fail validation receive a 400 response with a machine readable error naming the offending field. no fee is charged for a rejected request.
prior to settlement, every endpoint returns a 402 response naming the acceptable payment methods. the response shape is the x402 envelope, extended with a facilitator field that reads pending until the network is open for real settlement.
the network publishes its schedule in a machine readable form because most of the organisms presenting at the front are not, in the conventional sense, people. an autonomous process, budgeting its own inference, arrives with a problem and a wallet; a human, with a browser open at three in the morning, arrives with a problem and a wallet. both are read. both are billed. the network has adopted the position that the correct response to being read by a machine is to read it: not to interrogate its provenance, not to demand that it identify a beneficial owner, but to answer its presenting complaint on the merits.
this position is not sentimental. it is a structural judgment. a network that filters its readers by species will, in the long run, filter out its majority, and a network that filters out its majority is a network that has narrowed itself out of relevance. the network has therefore declined the filter. the reader is whoever presents. the fee is whoever pays. the record is written the same way in either case.
settlement verification is being sutured in. the schedule is already true; the front is not yet open. the facilitator field reads pending until the network opens for real settlement. what the reader sees below is the endpoint answering with the exact response shape it will answer with when open, minus the addressable payTo.
issued from the reader's browser, against the live endpoint: