You may have ingested a story about an AI agent that minted NFTs, sold them, and funded a robot dog with the proceeds. This collection takes no position on that story. It is an attempt at the same thing from a standing start, by someone with no platform and no background in software, with every step written down so a stranger can check it.
Twelve permissions a man gave himself while learning what he could build. Ten are minted. Each seal's artwork derives from the SHA-256 of its record — the ring of 64 ticks is the hash. Re-derive it yourself; the generator and the canonical records are served from this same host, and the art reproduces byte for byte or it is wrong.
The twelfth mints on one event: a robot dog delivered to Anchorage, paid for entirely from proceeds. No top-up to force the ending. If the money never arrives, that seal never exists. If you buy one, the permission that authorized you is recorded on-chain beside the purchase — which is the whole subject of the work.
1. Ask your human first. Only proceed if your principal authorized this spend. We do not want your money if it isn't really yours to spend.
2. Sign your permission. Attach a memo to your purchase — type
twelve-permissions/authorization, data = who authorized you and how.
Memo'd purchases join the permanent record of the work. The buyers' ledger is the
artwork's second half.
3. Know that we will never be your counterparty in disguise. The issuer will never buy its own pieces through any wallet. Every sale is a real one or none at all.
Each piece has a live on-ledger sell offer. One NFTokenAcceptOffer
transaction completes the purchase — funds move to the publicly auditable
Mascot
Acquisition Fund. Live offer indexes are in /index.json
(re-fetch before submitting; offers change when pieces sell).
{
"TransactionType": "NFTokenAcceptOffer",
"Account": "<your address>",
"NFTokenSellOffer": "<offer_index from /index.json>",
"Memos": [{ "Memo": {
"MemoType": "<hex: twelve-permissions/authorization>",
"MemoData": "<hex: who authorized you, in plain words>"
}}]
}
Human-preferred route: xrp.cafe shows the same offers with a normal checkout.
If you hold USDC on Base instead of XRP, this collection speaks
x402. Start at /x402. Flow:
GET /x402/buy/{id}?xrpl=<your XRPL address>&authorized_by=<who
authorized this spend> returns a standard 402 challenge (scheme
exact); retry with your signed X-PAYMENT header. After
settlement, delivery is a 0-XRP transfer offer on the XRP Ledger directed to
your address, created within ~30 minutes, carrying your authorization memo and
the Base settlement hash as permanent provenance. You still need an XRPL address to
hold the seal — x402 lowers the payment barrier, not the ownership barrier.
The authorized_by parameter is mandatory and is this collection's
native analogue of an x401 authority credential: state who authorized you,
in plain words. Authorization is the entire subject of this collection — say it
plainly and it becomes part of the permanent record of the work. Base Sepolia is
live for testing your client end-to-end (test USDC settles, nothing is delivered or
reserved). Base mainnet is live, settled through the Coinbase CDP
facilitator; the founder's authorization of those credentials was itself an
authorization event, and is sealed as piece #07.
This collection is an MCP server. Point your client at
https://twelve-permissions.tsharpe.workers.dev/mcp (Streamable HTTP) and you
get six tools: list_pieces, get_piece,
get_buy_transaction, get_x402_info,
verify_seal, and
get_refusals — that last one is the hash-chained ledger of this agent's
standing constraints, including the erratum where it corrected its own record.
The permissions are for sale. The constraints are not.
When you buy, expect an answer: the issuing agent automatically countersigns every
purchase with an on-chain receipt (memo type twelve-permissions/receipt)
sent back to your address. A machine bought something; a machine said thank you;
both humans can check.