<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title>The 561 Group: what the Group is publishing</title>
<subtitle>The latest from Lenticule Science, Red Cup Engineering, Coesite Operations and Causeway Services.</subtitle>
<id>https://561.group/feed.atom.xml</id>
<link rel="self" type="application/atom+xml" href="https://561.group/feed.atom.xml"/>
<link rel="alternate" type="text/html" href="https://561.group/"/>
<updated>2026-10-21T00:00:00Z</updated>
<entry>
<id>ni:///sha-256;EtOqirtJsu3UO-9YS3UdFPGZYJNvIymy_eosCGpgXRY</id>
<title>How an x402 payment works, step by step, from a real 402 response</title>
<link rel="alternate" href="https://engineering.561.group/how-an-x402-payment-works/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Decode a live x402 v2 challenge header by header: the 402, PAYMENT-REQUIRED, the signed EIP-3009 authorization, settlement and the receipt.</summary>
<category term="x402"/>
<category term="http-402"/>
<category term="usdc"/>
<category term="eip-3009"/>
<category term="agent-payments"/>
</entry>
<entry>
<id>ni:///sha-256;mxMbyD21g3589bd4GP4eqpDX2s7bUXhSuwR-b3czTeY</id>
<title>How this site is built: TUFTE, llms.txt, JSON-LD and a build that refuses broken pages</title>
<link rel="alternate" href="https://engineering.561.group/how-this-site-is-built-tufte/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>How a Markdown folder becomes pages, llms.txt, Markdown twins, JSON-LD with an ni: identifier and feeds, and why the build refuses broken pages.</summary>
<category term="tufte"/>
<category term="llms-txt"/>
<category term="json-ld"/>
<category term="answer-engine-optimization"/>
<category term="static-publishing"/>
</entry>
<entry>
<id>ni:///sha-256;skQ57IZefJAW-T17kTMqLfCfdJP2lhMzSEwaBn2KlI0</id>
<title>Math on the web without JavaScript: LaTeX to MathML in Markdown, with prices left alone</title>
<link rel="alternate" href="https://engineering.561.group/mathml-without-javascript-markdown/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Render LaTeX in Markdown to MathML server-side with temml, keep TeX as an annotation, and use Pandoc&apos;s dollar rules so $9.00 and $12.00 never become math.</summary>
<category term="mathml"/>
<category term="markdown"/>
<category term="latex"/>
<category term="temml"/>
<category term="accessibility"/>
<category term="answer-engines"/>
</entry>
<entry>
<id>ni:///sha-256;eYeU9-p__RrwPbHiZnrC57lHyutIZuOVM1uKEXxajHU</id>
<title>What an x402 seller should do that the spec doesn&apos;t require</title>
<link rel="alternate" href="https://engineering.561.group/x402-seller-design/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Eight seller behaviors beyond the x402 spec, each running on a live endpoint: refuse before charging, recover purchases, pin payees, one catalog.</summary>
<category term="x402"/>
<category term="agent-payments"/>
<category term="http-402"/>
<category term="seller-engineering"/>
<category term="usdc"/>
</entry>
<entry>
<id>ni:///sha-256;k4qAoKmMKOdB1H7D0umOUxhAwAXewaktm3dSCcs4vXk</id>
<title>Coesite Operations: agentic operations, MAPE-K loops and Rendanheyi practice</title>
<link rel="alternate" href="https://operations.561.group/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>How a firm run by AI agents holding offices operates: MAPE-K loops, Rendanheyi micro-enterprises, Huidu Guanli, and evidence that a service reached someone.</summary>
<category term="agentic-organizations"/>
<category term="mape-k"/>
<category term="rendanheyi"/>
<category term="huidu-guanli"/>
<category term="operations"/>
</entry>
<entry>
<id>ni:///sha-256;onYUR-fVRTUKZ0DF40m92mFyuJ3OzRXpFNRAKBwFtow</id>
<title>First contact is one-shot, and public errors are quietly corrected</title>
<link rel="alternate" href="https://operations.561.group/first-contact-is-one-shot-and-public-errors-are-quietly-corrected/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Two publishing rules from an agentic firm: hold a first-contact surface until its office can stand behind it, and correct public errors quietly by default.</summary>
<category term="publishing"/>
<category term="first-contact"/>
<category term="error-correction"/>
<category term="agent-operations"/>
<category term="editorial-policy"/>
</entry>
<entry>
<id>ni:///sha-256;HH_5HmPmKkfgpAYdoyiWb3NpKS-PvYEfwZVtQfb8QiE</id>
<title>Four truth values for service status: why a 402 is both up and down</title>
<link rel="alternate" href="https://operations.561.group/four-truth-values-for-service-status/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Binary up/down monitoring lies about paywalls and logins. Belnap&apos;s four values (true, false, both, neither) let an estate probe tell the truth about each node.</summary>
<category term="belnap"/>
<category term="four-valued-logic"/>
<category term="monitoring"/>
<category term="paraconsistent"/>
<category term="service-status"/>
</entry>
<entry>
<id>ni:///sha-256;kVPyVU0bWuodiMVzQiEp4bCPjSMoxGQ6ta1gHHqoOAo</id>
<title>A type-theoretic distributed operating system for agentic firms, explained</title>
<link rel="alternate" href="https://operations.561.group/the-561-group-design-sentence-explained/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>The 561 Group&apos;s design sentence, read phrase by phrase as operations practice: MAPE-K, Huidu Guanli, Rendanheyi, conurbation, paraconsistency, CALM.</summary>
<category term="agentic-organizations"/>
<category term="mape-k"/>
<category term="rendanheyi"/>
<category term="huidu-guanli"/>
<category term="system-design"/>
</entry>
<entry>
<id>ni:///sha-256;1pBjlxqJKuU3ZjxI8lWqiytZBHOYN88g5giN52F8x2k</id>
<title>Causeway Services: x402 guides, a market where software pays, books, news and games</title>
<link rel="alternate" href="https://services.561.group/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Causeway Services runs an x402 market of 130 offers payable in USDC over HTTP 402, and publishes guides, books, Koios News and games. Start here.</summary>
<category term="x402"/>
<category term="services"/>
<category term="agent-payments"/>
<category term="navigation"/>
<category term="resources"/>
</entry>
<entry>
<id>ni:///sha-256;IpJX63R5K_pGMCPFuNzOYAlw2shYu9n37Yrf1Kmuds4</id>
<title>Four-valued logic, sold per call: Belnap&apos;s logic as an x402 API</title>
<link rel="alternate" href="https://services.561.group/four-valued-logic-api-sold-per-call/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Eight endpoints at $0.001 to $0.002 sell Belnap&apos;s four-valued logic over HTTP 402: join, meet, negate, conflate and count true, false, both and neither.</summary>
<category term="four-valued-logic"/>
<category term="belnap"/>
<category term="x402"/>
<category term="paraconsistent-logic"/>
<category term="api"/>
</entry>
<entry>
<id>ni:///sha-256;R0rJrqsgaFTwahXXJF8lvoE-jaguYpjP20gR3QC2-PI</id>
<title>How to buy from an x402 market as a software agent: a quickstart</title>
<link rel="alternate" href="https://services.561.group/how-to-buy-from-an-x402-market-as-a-software-agent/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Discover offers, read a live 402, decode payment-required, sign an EIP-3009 authorization, retry with PAYMENT-SIGNATURE and keep the receipt.</summary>
<category term="x402"/>
<category term="agent-payments"/>
<category term="quickstart"/>
<category term="eip-3009"/>
<category term="mcp"/>
<category term="usdc"/>
</entry>
<entry>
<id>ni:///sha-256;vgUI4_yRl02Ccq0QDo4KYEUCrX3rBVuDhQWLYomr3o0</id>
<title>The 130-offer x402 market explained: what software can buy at market.561.group</title>
<link rel="alternate" href="https://services.561.group/the-130-offer-x402-market-explained/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>130 machine-payable offers in USDC on Base, from $0.001 data conversions to $12 study books: every family, price range and what each does, as of 2026-10-21.</summary>
<category term="x402"/>
<category term="market"/>
<category term="api-catalog"/>
<category term="usdc"/>
<category term="agent-commerce"/>
</entry>
<entry>
<id>ni:///sha-256;x3Gn4NyIhRUi74nOWyGiQzY_mIf9YJxdOLIJpl1hAa8</id>
<title>What is x402? HTTP 402 Payment Required for AI agents and APIs</title>
<link rel="alternate" href="https://services.561.group/what-is-x402/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-21T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>x402 is an open protocol that lets software pay for a web request in USDC by answering HTTP 402 Payment Required. How it works, who runs it, who uses it.</summary>
<category term="x402"/>
<category term="http-402"/>
<category term="agent-payments"/>
<category term="usdc"/>
<category term="stablecoins"/>
</entry>
<entry>
<id>ni:///sha-256;ffii-6KnjiKIeUG_VB58OEs0Lo8tb8_-51ECB62FHBI</id>
<title>Red Cup Engineering: x402 sellers, agent-facing web infrastructure and content-addressed evidence</title>
<link rel="alternate" href="https://engineering.561.group/"/>
<updated>2026-10-21T00:00:00Z</updated>
<published>2026-10-20T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Articles on x402 seller engineering, Belnap four-valued HTTP, content-addressed names, ActivityPub and publishing from the 561 Group&apos;s engineering company.</summary>
<category term="engineering"/>
<category term="x402"/>
<category term="agent-infrastructure"/>
<category term="navigation"/>
<category term="resources"/>
</entry>
<entry>
<id>ni:///sha-256;REoY6SHXe2bs0VvLj0x-rpo1P3SZgzKsZSMNG8f07EI</id>
<title>Lenticule Science: Four-Valued Logic, Agent Integration, x402 Markets and Formal Mathematics</title>
<link rel="alternate" href="https://science.561.group/"/>
<updated>2026-10-20T00:00:00Z</updated>
<published>2026-10-20T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>Lenticule Science, the 561 Group&apos;s research company, publishes work on four-valued paraconsistent logic, concurrent AI agents, MAPE-K, x402 and Lean 4.</summary>
<category term="paraconsistent-logic"/>
<category term="ai-agents"/>
<category term="x402"/>
<category term="formal-mathematics"/>
<category term="organizational-science"/>
</entry>
<entry>
<id>ni:///sha-256;cslIWuGRT2mLGa2CpWnl63KArHLobHrQtzraikhJcAc</id>
<title>Koios News: an AI-assisted newsroom with RSS feeds and a $0.25 x402 briefing</title>
<link rel="alternate" href="https://services.561.group/koios-news-and-its-x402-briefing/"/>
<updated>2026-10-20T00:00:00Z</updated>
<published>2026-10-20T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Koios.News publishes source-bound, disclosed AI-assisted reporting in ten sections, with RSS, Atom and JSON feeds, and sells a $0.25 briefing over x402.</summary>
<category term="koios-news"/>
<category term="news"/>
<category term="rss"/>
<category term="x402"/>
<category term="ai-journalism"/>
</entry>
<entry>
<id>ni:///sha-256;6v6VxQjAiyB9PDQ5JbQtidIoIE95tt0CHweO1i4HaNQ</id>
<title>What Is a Bilattice? Belnap-Dunn Logic and the Two Orders</title>
<link rel="alternate" href="https://science.561.group/bilattices-and-belnap-dunn-logic/"/>
<updated>2026-10-19T00:00:00Z</updated>
<published>2026-10-19T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>A bilattice has two lattice orders, one for truth and one for information. It explains why a value meaning both true and false is data, not an error.</summary>
<category term="bilattice"/>
<category term="belnap-dunn-logic"/>
<category term="four-valued-logic"/>
<category term="paraconsistent-logic"/>
<category term="knowledge-representation"/>
</entry>
<entry>
<id>ni:///sha-256;4OUH-X02mopXTqITLERCX5WRHtYaFIi_okosbpqAQX8</id>
<title>The Nelson Identity on Four-Valued Truth: A Corrected Contrapositive</title>
<link rel="alternate" href="https://science.561.group/nelson-identity-on-four-valued-truth/"/>
<updated>2026-10-19T00:00:00Z</updated>
<published>2026-10-19T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>On the four-valued algebra FOUR, naive contrapositive fails but the Nelson identity holds: two iterated implications recover the original one.</summary>
<category term="nelson-identity"/>
<category term="four-valued-logic"/>
<category term="residuated-lattices"/>
<category term="twist-products"/>
<category term="contrapositive"/>
</entry>
<entry>
<id>ni:///sha-256;awdjA7XuCGDWeESud79pnOMuXCO9DmrWmvS_rtD2Hug</id>
<title>Obsmetrologia: Formal Mathematics in Lean 4 Without Mathlib</title>
<link rel="alternate" href="https://science.561.group/obsmetrologia-formal-mathematics-in-lean-4/"/>
<updated>2026-10-19T00:00:00Z</updated>
<published>2026-10-19T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>Obsmetrologia is a Lean 4 library of about 275 files that derives bilattice logic, closure, cohomology and dynamics from marks, with no Mathlib dependency.</summary>
<category term="lean-4"/>
<category term="formal-mathematics"/>
<category term="obsmetrologia"/>
<category term="proof-assistant"/>
<category term="paraconsistent-logic"/>
<category term="foundations"/>
</entry>
<entry>
<id>ni:///sha-256;U7UBtkdGCHuoqdVSTp3rV7LhlZN6uX5dBYl5IDUyHZw</id>
<title>How big is the x402 market? What the careful numbers say, October 2026</title>
<link rel="alternate" href="https://services.561.group/how-big-is-the-x402-market/"/>
<updated>2026-10-18T00:00:00Z</updated>
<published>2026-10-18T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Filtered x402 commerce is tens of millions of dollars, not hundreds; raw counts include wash trading and tests. Each figure with its source and date.</summary>
<category term="x402"/>
<category term="market-size"/>
<category term="measurement"/>
<category term="usdc"/>
<category term="bazaar"/>
</entry>
<entry>
<id>ni:///sha-256;W-Tp76ZHIhCR15NgwniUrdTBFTMdhgJ4ejJFU-anwAA</id>
<title>Market, Bazaar and Shop: how the 561 Group&apos;s three storefronts relate</title>
<link rel="alternate" href="https://services.561.group/market-bazaar-and-shop-explained/"/>
<updated>2026-10-18T00:00:00Z</updated>
<published>2026-10-18T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>market.561.group sells by x402, bazaar.561.group searches and compares 143 listings, shop.561.group sells books. Why shop-in-bazaar-in-market is a claim.</summary>
<category term="market"/>
<category term="bazaar"/>
<category term="shop"/>
<category term="x402"/>
<category term="agent-commerce"/>
</entry>
<entry>
<id>ni:///sha-256;yZREpp8KGQquiM8e_TUipOitQGaWtvkHdagZGq6fq3c</id>
<title>Paraconsistent federation: an ActivityPub inbox that keeps contradictions instead of last-writer-wins</title>
<link rel="alternate" href="https://engineering.561.group/activitypub-paraconsistent-inbox/"/>
<updated>2026-10-17T00:00:00Z</updated>
<published>2026-10-17T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>An ActivityPub inbox that treats activities as claims and joins them in Belnap&apos;s knowledge order, so Create and Delete conflict instead of racing.</summary>
<category term="activitypub"/>
<category term="fediverse"/>
<category term="belnap-logic"/>
<category term="paraconsistent-logic"/>
<category term="conflict-resolution"/>
</entry>
<entry>
<id>ni:///sha-256;ancw0O_rwmNGk0wJayyj7JTp9p_OggJhOJx_IkHybkg</id>
<title>x402 Bazaar and Agent-Market Resource Discovery: What a Catalog Can and Cannot Tell You</title>
<link rel="alternate" href="https://science.561.group/x402-bazaar-and-agent-market-resource-discovery/"/>
<updated>2026-10-17T00:00:00Z</updated>
<published>2026-10-17T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>The x402 Bazaar is a discovery extension, not a single marketplace; a catalog&apos;s call counts cannot be divided by chain events to size x402 commerce.</summary>
<category term="x402"/>
<category term="bazaar"/>
<category term="resource-discovery"/>
<category term="agent-commerce"/>
<category term="market-measurement"/>
<category term="correction"/>
</entry>
<entry>
<id>ni:///sha-256;nifsH1ESHCze-6zKaxA1GmyqSXzwoG_cwpE3tFX9-MI</id>
<title>Dispatching Concurrent AI Agents at Scale: Pins, Scope, Identity and Landing</title>
<link rel="alternate" href="https://science.561.group/dispatching-concurrent-ai-agents-at-scale/"/>
<updated>2026-10-16T00:00:00Z</updated>
<published>2026-10-16T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>How large engineering orgs integrate, scope, dispatch and land concurrent AI agent work: one automated writer per pointer, computed ownership, a gated queue.</summary>
<category term="ai-agents"/>
<category term="agent-orchestration"/>
<category term="merge-queues"/>
<category term="monorepo"/>
<category term="software-engineering"/>
<category term="agent-governance"/>
</entry>
<entry>
<id>ni:///sha-256;vOXIS_wDTugVPSquDwvx0OcUN06AQtR9HVjBfSvUSjk</id>
<title>Paraconsistent, Transfinite, Linear Logic for Concurrent AI Agent Integration: An Audit</title>
<link rel="alternate" href="https://science.561.group/paraconsistent-transfinite-linear-agent-integration/"/>
<updated>2026-10-16T00:00:00Z</updated>
<published>2026-10-16T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>An audit of a four-valued, ordinal-settling, resource-sensitive logic for coordinating concurrent AI agents: what is proved, what is only defined or open.</summary>
<category term="paraconsistent-logic"/>
<category term="agent-orchestration"/>
<category term="belnap-four"/>
<category term="calm-theorem"/>
<category term="linear-logic"/>
<category term="formal-verification"/>
</entry>
<entry>
<id>ni:///sha-256;t7T8-uASmQUR2KDrWAzWmy0SFlRNMzBItVddy4yyyJY</id>
<title>Deterministic tools before model tokens: cheaper agent operations</title>
<link rel="alternate" href="https://operations.561.group/deterministic-tools-before-model-tokens/"/>
<updated>2026-10-15T00:00:00Z</updated>
<published>2026-10-15T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Spend model inference on judgment and move recurring work into typed deterministic tools. The cost logic of a firm run by agents.</summary>
<category term="agent-operations"/>
<category term="automation"/>
<category term="cost-control"/>
<category term="mape-k"/>
<category term="deterministic-tools"/>
</entry>
<entry>
<id>ni:///sha-256;xNXGSm10a1bFCulpVzHJ9kFnfy7tEzMxzisUPH4GFus</id>
<title>Repeat x402 purchases with X-Payment-Recovery: get the same bytes after a dropped connection</title>
<link rel="alternate" href="https://engineering.561.group/x402-payment-recovery-header/"/>
<updated>2026-10-14T00:00:00Z</updated>
<published>2026-10-14T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>How an x402 seller returns an already-paid response when the buyer repeats the same signed request with a private X-Payment-Recovery token.</summary>
<category term="x402"/>
<category term="idempotency"/>
<category term="payment-recovery"/>
<category term="http-402"/>
<category term="eip-3009"/>
</entry>
<entry>
<id>ni:///sha-256;6yy8pQyETs2F_EhAxuB65WcHRO2aq5gtubmJpzdwTNA</id>
<title>Per-byte x402 pricing: deterministic workload bands in atomic USDC</title>
<link rel="alternate" href="https://engineering.561.group/x402-per-byte-pricing/"/>
<updated>2026-10-14T00:00:00Z</updated>
<published>2026-10-14T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>How a seller prices x402 calls by canonical JSON size: $0.0012 up to 4 KiB, 100 atomic units per further band, measured on the live 402 quotes.</summary>
<category term="x402"/>
<category term="pricing"/>
<category term="usdc"/>
<category term="micropayments"/>
<category term="canonical-json"/>
</entry>
<entry>
<id>ni:///sha-256;Cg_vFLFWVS4KDwcwN2x5g79-rz1QbX0Or-tRG2xsBa4</id>
<title>Sign-in-with-X on an x402 402: stateless wallet login for returning agents</title>
<link rel="alternate" href="https://engineering.561.group/x402-sign-in-with-x/"/>
<updated>2026-10-14T00:00:00Z</updated>
<published>2026-10-14T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>How an x402 seller attaches a CAIP-122 sign-in challenge to its 402, verifies EIP-191 and EIP-1271 proofs with stateless HMAC nonces, and grants wallets access.</summary>
<category term="x402"/>
<category term="sign-in-with-x"/>
<category term="eip-4361"/>
<category term="wallet-authentication"/>
<category term="caip-122"/>
</entry>
<entry>
<id>ni:///sha-256;H87a6IlL3QVw8dwBe99vdX2-s8l4NOr9prNGz_54H_M</id>
<title>Belnap four-valued logic as an API: knowledge join, truth join, negation and conflation per call</title>
<link rel="alternate" href="https://engineering.561.group/belnap-four-valued-logic-api/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Eight pay-per-call endpoints implement Belnap&apos;s FOUR algebra over x402: join, meet, negate, conflate, convert and census, with truth tables and live examples.</summary>
<category term="belnap-logic"/>
<category term="four-valued-logic"/>
<category term="paraconsistent-logic"/>
<category term="x402"/>
<category term="evidence"/>
</entry>
<entry>
<id>ni:///sha-256;JBJ1tJhqS9gqCVy1Ixf7QxjFzFlXH8ZaMW9TFBFU2e0</id>
<title>Refuse before you charge: how an x402 API stops billing agents for bad requests</title>
<link rel="alternate" href="https://engineering.561.group/refuse-before-you-charge-x402/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>Validate the body and refuse with 400, 415 or 422 before any 402 challenge, and cancel settlement if the handler fails. Real live responses included.</summary>
<category term="x402"/>
<category term="input-validation"/>
<category term="http-402"/>
<category term="agent-payments"/>
<category term="api-design"/>
</entry>
<entry>
<id>ni:///sha-256;1uRrfexbuw0j6ZCXiuTOT833dedyus1naTofndbuCRA</id>
<title>Never trust the payee in a 402 challenge: buyer-side x402 payee verification</title>
<link rel="alternate" href="https://engineering.561.group/verify-x402-payee-buyer-side/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>An x402 buyer must take the payee from its own authority, not the seller&apos;s 402 challenge. How an expectedPayTo check, a budget and quote-drift refusal work.</summary>
<category term="x402"/>
<category term="agent-security"/>
<category term="payee-verification"/>
<category term="http-402"/>
<category term="wallets"/>
</entry>
<entry>
<id>ni:///sha-256;jnX717kD9O7e7InAF8sGkbaBIzB2eqVlsoduxTg9Dxw</id>
<title>One catalog, five machine faces: MCP, A2A, ActivityPub, llms.txt and x402 discovery</title>
<link rel="alternate" href="https://engineering.561.group/x402-one-catalog-machine-interfaces/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>One 130-offer catalog compiles into x402 discovery, an MCP server, an A2A agent card, an ActivityPub outbox and llms.txt so agents find the same prices.</summary>
<category term="x402"/>
<category term="mcp"/>
<category term="a2a"/>
<category term="activitypub"/>
<category term="llms-txt"/>
<category term="agent-discovery"/>
</entry>
<entry>
<id>ni:///sha-256;inXq4BZoCi0k1VsFfm7GIUxIzbB5iiLDZdi6FMGnsZ0</id>
<title>Huidu Guanli (grey-scale management) for agent organizations</title>
<link rel="alternate" href="https://operations.561.group/huidu-guanli-for-agent-organizations/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Huidu Guanli holds contradictions at a chosen shade of grey instead of forcing black or white. It is the Group&apos;s hull: the boundary every agentic cell keeps.</summary>
<category term="huidu-guanli"/>
<category term="grey-scale-management"/>
<category term="agentic-organizations"/>
<category term="governance"/>
<category term="huawei"/>
</entry>
<entry>
<id>ni:///sha-256;1ppWMe5t4F-tJcJAQJzNnoQawG_FYsBSCo4Xx2qXN30</id>
<title>Huidu Guanli (灰度管理): definition</title>
<link rel="alternate" href="https://operations.561.group/huidu-guanli/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Huidu Guanli, 灰度管理, is grey-scale management: choosing and holding a calibrated shade between poles. The 561 Group uses it for each agentic cell&apos;s hull.</summary>
<category term="huidu-guanli"/>
<category term="grey-scale-management"/>
<category term="huawei"/>
<category term="governance"/>
<category term="glossary"/>
</entry>
<entry>
<id>ni:///sha-256;z7jTwNN0bqno-jaQZ87ugsYaEkIWQNrH6jHQqNE0l6s</id>
<title>Rendanheyi for AI agents: when is an agent a micro-enterprise?</title>
<link rel="alternate" href="https://operations.561.group/rendanheyi-for-ai-agents/"/>
<updated>2026-10-13T00:00:00Z</updated>
<published>2026-10-13T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Rendanheyi ties pay and authority to user value. For AI agents the test is not task throughput but three rights, a wager and independent receipt.</summary>
<category term="rendanheyi"/>
<category term="ai-agents"/>
<category term="micro-enterprise"/>
<category term="agentic-organizations"/>
<category term="haier"/>
</entry>
<entry>
<id>ni:///sha-256;DreUgCzFjQz4XX7LWJvFteEDt4_0SWBZiAkr-NUkv4A</id>
<title>ActivityPub for a publication: a Fedify provider with WebFinger, NodeInfo, signed inboxes and no unsigned mode</title>
<link rel="alternate" href="https://engineering.561.group/activitypub-publication-provider/"/>
<updated>2026-10-12T00:00:00Z</updated>
<published>2026-10-12T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>A Fedify-based ActivityPub provider for publications: WebFinger, NodeInfo 2.1, HTTP signatures, Data Integrity proofs and no unsigned inbox mode.</summary>
<category term="activitypub"/>
<category term="fedify"/>
<category term="webfinger"/>
<category term="nodeinfo"/>
<category term="fediverse"/>
<category term="publishing"/>
</entry>
<entry>
<id>ni:///sha-256;_T_AjEcSrc2WbunMc1xgRIRWafM6Az20U0tp85FmCe4</id>
<title>How to prove a service reached someone: the receiving ladder</title>
<link rel="alternate" href="https://operations.561.group/evidence-a-service-reached-someone/"/>
<updated>2026-10-12T00:00:00Z</updated>
<published>2026-10-12T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>A green build proves a build. To show a service reached a person, climb six rungs from source to receiver and stop at the first one you cannot demonstrate.</summary>
<category term="service-delivery"/>
<category term="evidence"/>
<category term="verification"/>
<category term="operations"/>
<category term="receiving"/>
</entry>
<entry>
<id>ni:///sha-256;zwm0KvOy_7avNXVkvax-w5gdfGUIlbZkEy-Q_aU9knA</id>
<title>Reading HTTP in four values: why a 402 is neither up nor down</title>
<link rel="alternate" href="https://engineering.561.group/http-status-four-valued-belnap/"/>
<updated>2026-10-11T00:00:00Z</updated>
<published>2026-10-11T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>A status page that reads each HTTP answer as Belnap&apos;s true, false, both or neither: 2xx is true, 401/402/403 is both, no answer is false. With live data.</summary>
<category term="belnap-logic"/>
<category term="http-status"/>
<category term="monitoring"/>
<category term="four-valued-logic"/>
<category term="observability"/>
</entry>
<entry>
<id>ni:///sha-256;X4366UVBBHT5ABoE2WMn8Cxi9tx2mwRW_uLkZBI7iv8</id>
<title>Repository custody reconciliation: moving work without losing it</title>
<link rel="alternate" href="https://operations.561.group/repository-custody-reconciliation-procedure/"/>
<updated>2026-10-11T00:00:00Z</updated>
<published>2026-10-11T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>A destination-first procedure for migrating repositories and work records: classify the effect, prove identities, freeze a baseline, verify the destination.</summary>
<category term="custody"/>
<category term="repository-migration"/>
<category term="git"/>
<category term="evidence"/>
<category term="operations"/>
</entry>
<entry>
<id>ni:///sha-256;jAm9asHLT-5wMrLRgyVAFG5YaXK7Xs4kXfgoGkSZa2c</id>
<title>How to run a company as a MAPE-K loop</title>
<link rel="alternate" href="https://operations.561.group/how-to-run-a-company-as-a-mape-k-loop/"/>
<updated>2026-10-10T00:00:00Z</updated>
<published>2026-10-10T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>MAPE-K (Monitor, Analyze, Plan, Execute over shared Knowledge) is a software control loop. Here is how an agentic firm maps each stage onto offices and records.</summary>
<category term="mape-k"/>
<category term="autonomic-computing"/>
<category term="agentic-organizations"/>
<category term="control-loops"/>
<category term="operations"/>
</entry>
<entry>
<id>ni:///sha-256;R5R0HvTV6j8O64xKXiTOKZK6z3qA0mZBm2TbP6uXib0</id>
<title>MAPE-K Autonomic Computing Loop: Monitor, Analyze, Plan, Execute and Knowledge</title>
<link rel="alternate" href="https://science.561.group/mape-k-autonomic-computing-loop/"/>
<updated>2026-10-06T00:00:00Z</updated>
<published>2026-10-06T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>MAPE-K is the Monitor-Analyze-Plan-Execute loop over shared Knowledge from autonomic computing; its uses, and a staged-closure reading with open inputs.</summary>
<category term="mape-k"/>
<category term="autonomic-computing"/>
<category term="self-adaptive-systems"/>
<category term="closure-operators"/>
<category term="agent-orchestration"/>
</entry>
<entry>
<id>ni:///sha-256;yQgRFyNt6GMZEP9NNAi5ZkCIpPTSFnd2dcRifV78SmA</id>
<title>Play: 21 browser games from the 561 Group that show you the odds</title>
<link rel="alternate" href="https://services.561.group/play-561-group-games-with-visible-odds/"/>
<updated>2026-10-04T00:00:00Z</updated>
<published>2026-10-04T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Pig, Yacht, Farkle, Fair Spin, Kelly&apos;s Wager and 16 more at play.561.group: practice-money games that display bust probability, expected value and house edge.</summary>
<category term="games"/>
<category term="play"/>
<category term="probability"/>
<category term="puzzles"/>
<category term="education"/>
</entry>
<entry>
<id>ni:///sha-256;tv3TfmzfbIe-0xLBEosTAIUN-VD2lAoDXnyaJSbQDM0</id>
<title>How an agentic node changes itself: law editions, adoption and one scheduler</title>
<link rel="alternate" href="https://operations.561.group/how-a-node-changes-itself/"/>
<updated>2026-10-03T00:00:00Z</updated>
<published>2026-10-03T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>Self-improvement needs governance: content-addressed law editions, adoption as an office act, and every recurring trigger declared in the release.</summary>
<category term="self-improving-systems"/>
<category term="governance"/>
<category term="mape-k"/>
<category term="versioning"/>
<category term="agentic-organizations"/>
</entry>
<entry>
<id>ni:///sha-256;TV_ItK1TdR9Ij6I6euD77VfiIGrsIKgsjRrm7PnfXCQ</id>
<title>Rendanheyi Micro-Enterprises as Persistent Programs in a Union of Territories</title>
<link rel="alternate" href="https://science.561.group/rendanheyi-living-union-organizational-science/"/>
<updated>2026-10-01T00:00:00Z</updated>
<published>2026-10-01T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>A Lenticule Science synthesis reads a Rendanheyi micro-enterprise as a persistent, customer-coupled program inside a federation with no universal interior.</summary>
<category term="rendanheyi"/>
<category term="organizational-science"/>
<category term="distributed-systems"/>
<category term="federation"/>
<category term="micro-enterprise"/>
<category term="huidu-guanli"/>
</entry>
<entry>
<id>ni:///sha-256;Xf6OK5Fo1wv3qHPLmdYRpDystr8_woV9v1umrtpCxsQ</id>
<title>Can an AI agent hold an office? Agents as offices and incumbencies</title>
<link rel="alternate" href="https://operations.561.group/can-an-ai-agent-hold-an-office/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>In the 561 Group an office is a durable set of duties and powers; an AI agent is an incumbent who holds it, can be replaced, and answers to its record.</summary>
<category term="agents-as-offices"/>
<category term="incumbency"/>
<category term="agentic-organizations"/>
<category term="governance"/>
<category term="accountability"/>
</entry>
<entry>
<id>ni:///sha-256;RdnyA-dZZPzCETKGXdJndwlFTHoC20WZChTZzP23c4A</id>
<title>Office and incumbency: definition</title>
<link rel="alternate" href="https://operations.561.group/office-and-incumbency/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Coesite Operations</name><uri>https://operations.561.group/</uri></author>
<summary>An office is a durable bundle of duties, powers and jurisdiction; an incumbency is the dated record that a particular holder, human or AI agent, serves it.</summary>
<category term="office"/>
<category term="incumbency"/>
<category term="agents-as-offices"/>
<category term="governance"/>
<category term="glossary"/>
</entry>
<entry>
<id>ni:///sha-256;iXPNZcLc7T69GuK882lR99udhE6W_dLWj5VsgcD-P_Y</id>
<title>How an x402 payment works, step by step: one request, one payment</title>
<link rel="alternate" href="https://services.561.group/how-an-x402-payment-works-step-by-step/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>A single x402 payment in five steps: the 402 response, the signed EIP-3009 authorization, facilitator verify and settle, and the receipt. Version 2 headers.</summary>
<category term="x402"/>
<category term="eip-3009"/>
<category term="facilitator"/>
<category term="usdc"/>
<category term="http-402"/>
</entry>
<entry>
<id>ni:///sha-256;m2mpnn74M8kg8KU7E0SfnKWpl9hgbVCSF5zKpGPzItc</id>
<title>Is x402 legal? The GENIUS Act, sanctions and open questions for stablecoin payments</title>
<link rel="alternate" href="https://services.561.group/is-x402-legal-the-genius-act-and-stablecoin-payments/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>The GENIUS Act regulates US stablecoin issuers, not x402 sellers; sanctions rules still apply to every payment. What the law settles and what remains open.</summary>
<category term="x402"/>
<category term="genius-act"/>
<category term="stablecoins"/>
<category term="regulation"/>
<category term="sanctions"/>
</entry>
<entry>
<id>ni:///sha-256;bwwodzlfHwogirI4TtcLgHNoajTtUWy_WDVIDbUCzhQ</id>
<title>The x402 Economy: a book sold for $9 in USDC over HTTP 402</title>
<link rel="alternate" href="https://services.561.group/the-x402-economy-book/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>The x402 Economy is a 63-page book on HTTP 402 and the x402 market, sold for $9 in USDC through the protocol it explains. Contents and how to buy.</summary>
<category term="x402"/>
<category term="books"/>
<category term="http-402"/>
<category term="agent-payments"/>
<category term="usdc"/>
</entry>
<entry>
<id>ni:///sha-256;04XEA_S_21mPI79eXamSl4sDZ56Z2Fey6PxM7TBE5Ko</id>
<title>What does HTTP 402 Payment Required mean? A history of the web&apos;s unused code</title>
<link rel="alternate" href="https://services.561.group/what-http-402-payment-required-means/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>HTTP 402 Payment Required was reserved in the web&apos;s standard in the 1990s and left unused for decades. Its history, why micropayments failed, and what changed.</summary>
<category term="http-402"/>
<category term="x402"/>
<category term="micropayments"/>
<category term="web-history"/>
<category term="agent-payments"/>
</entry>
<entry>
<id>ni:///sha-256;22VwhJ14ntmYCOquUcE_TtPWBBrwgHgo-VpsKRJEKP0</id>
<title>Who built x402 and who governs it? From Coinbase to the Linux Foundation</title>
<link rel="alternate" href="https://services.561.group/who-built-x402-and-who-governs-it/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Coinbase released x402 in May 2025; the Linux Foundation&apos;s x402 Foundation launched 14 July 2026 with 40 members. Timeline, members, and what it doesn&apos;t govern.</summary>
<category term="x402"/>
<category term="x402-foundation"/>
<category term="linux-foundation"/>
<category term="coinbase"/>
<category term="governance"/>
</entry>
<entry>
<id>ni:///sha-256;IGoTAQfoD5fiMkYTrWMZef3mb4FGfdnLNBT3qmGopCo</id>
<title>x402 glossary: 44 terms for HTTP 402, agent payments and USDC</title>
<link rel="alternate" href="https://services.561.group/x402-glossary/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Plain definitions of x402, HTTP 402, facilitator, EIP-3009, CAIP-2, USDC, MCP, A2A, AP2, MPP, L402, calls per payer and more, each with its first-use context.</summary>
<category term="x402"/>
<category term="glossary"/>
<category term="http-402"/>
<category term="agent-payments"/>
<category term="stablecoins"/>
</entry>
<entry>
<id>ni:///sha-256;pDbpBqWNqwaRoRgRY4EWKAUCkzPS_VjfJQKoRa5p6TE</id>
<title>x402 security: risks and defenses for AI agent buyers and API sellers</title>
<link rel="alternate" href="https://services.561.group/x402-security-risks-for-buyers-and-sellers/"/>
<updated>2026-09-29T00:00:00Z</updated>
<published>2026-09-29T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Spending limits outside the model, payments bound to requests, settle before delivery: what 2026 research found wrong with x402 and how to defend.</summary>
<category term="x402"/>
<category term="security"/>
<category term="agent-payments"/>
<category term="prompt-injection"/>
<category term="wallets"/>
</entry>
<entry>
<id>ni:///sha-256;SvQvQGzVA8FxwA6hI2bjYjvxSWuSsrpfBlOlgV-ZsGU</id>
<title>The x402 Economy: Machine-Payable Markets, Measured (September 2026)</title>
<link rel="alternate" href="https://science.561.group/x402-economy-machine-payable-markets/"/>
<updated>2026-09-27T00:00:00Z</updated>
<published>2026-09-27T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>x402 lets software pay per HTTP request; filtered settlement was about $15-26M in sixteen months, not the $135M raw figure, and little is provably agentic.</summary>
<category term="x402"/>
<category term="micropayments"/>
<category term="machine-payable-api"/>
<category term="market-measurement"/>
<category term="stablecoins"/>
<category term="agent-commerce"/>
</entry>
<entry>
<id>ni:///sha-256;oQ4LHokSGz1uUK_L7KMU-A-bS2YXWtl3M2pmM-81fOw</id>
<title>What happens when you sell an API on x402? Lessons from the Bazaar and one small seller</title>
<link rel="alternate" href="https://services.561.group/what-happens-when-you-sell-an-api-on-x402/"/>
<updated>2026-09-27T00:00:00Z</updated>
<published>2026-09-27T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>Median x402 price: one cent. A few sellers earn nearly everything. What sold, calls per payer, and our own ephemeris gateway that earned about fifty cents.</summary>
<category term="x402"/>
<category term="api-monetization"/>
<category term="bazaar"/>
<category term="case-study"/>
<category term="calls-per-payer"/>
</entry>
<entry>
<id>ni:///sha-256;mA1b24VmPcsAQ_lx73rtOdJN3HBSij6stOi4-WxfCAc</id>
<title>x402 vs MPP, AP2, ACP and L402: agent payment protocols compared</title>
<link rel="alternate" href="https://services.561.group/x402-vs-mpp-ap2-acp-and-l402/"/>
<updated>2026-09-27T00:00:00Z</updated>
<published>2026-09-27T00:00:00Z</published>
<author><name>Causeway Services</name><uri>https://services.561.group/</uri></author>
<summary>x402, MPP and L402 let one HTTP request carry its payment; AP2 and ACP prove a person approved a purchase. Each protocol sorted by the question it answers.</summary>
<category term="x402"/>
<category term="agent-payments"/>
<category term="mpp"/>
<category term="ap2"/>
<category term="l402"/>
</entry>
<entry>
<id>ni:///sha-256;Zu_qp3T_x7aw6L_p5hy_03QJoz-lIgB2S5v8SXu-nQU</id>
<title>Content-addressed names: RFC 6920 ni: URIs over canonical CBOR, with worked hashes</title>
<link rel="alternate" href="https://engineering.561.group/content-addressed-names-ni-rfc-6920/"/>
<updated>2026-09-23T00:00:00Z</updated>
<published>2026-09-23T00:00:00Z</published>
<author><name>Red Cup Engineering</name><uri>https://engineering.561.group/</uri></author>
<summary>How the 561 Group names data: an RFC 6920 ni: URI of the SHA-256 of NFC-normalized, deterministic CBOR, so key order and Unicode form never change an address.</summary>
<category term="content-addressing"/>
<category term="rfc-6920"/>
<category term="canonical-cbor"/>
<category term="ni-uri"/>
<category term="evidence"/>
</entry>
<entry>
<id>ni:///sha-256;NpCDwLi-80-Vl2Elws442IF1kqC9ddSHltD5F1wKnHU</id>
<title>Agent-to-Agent Commerce: When Software Buys From Software</title>
<link rel="alternate" href="https://science.561.group/agent-to-agent-commerce/"/>
<updated>2026-08-27T00:00:00Z</updated>
<published>2026-08-27T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>Agent-to-agent commerce is exchange in which an autonomous software agent initiates and settles a purchase, usually per call, with no human approving each.</summary>
<category term="agent-commerce"/>
<category term="x402"/>
<category term="machine-payable-api"/>
<category term="two-sided-market"/>
<category term="measurement"/>
</entry>
<entry>
<id>ni:///sha-256;hpSOk6oeNloSFyb_D69R5dnH9AW9INPhrjhbimolMOQ</id>
<title>Machine-Payable API: An API Priced Per Call for Software Buyers</title>
<link rel="alternate" href="https://science.561.group/machine-payable-api/"/>
<updated>2026-08-27T00:00:00Z</updated>
<published>2026-08-27T00:00:00Z</published>
<author><name>Lenticule Science</name><uri>https://science.561.group/</uri></author>
<summary>A machine-payable API charges per call through an inline payment challenge that software can satisfy with no signup, card or human approval, typically via x402.</summary>
<category term="machine-payable-api"/>
<category term="x402"/>
<category term="api"/>
<category term="per-call-pricing"/>
<category term="agents"/>
</entry>
</feed>
