Settlement evidence for autonomous payments.
Potential integration, commercial licensing or strategic technology review — backed by verifiable operator-funded payment canaries, with material limitations documented openly. No acquisition, valuation, customer traction or IP ownership has been independently certified.
Observable assets for a potential buyer to inspect
Agent Settlement Passport
Quorum of two from three public Base RPC providers, native USDC receipt/payee/amount/depth checks, and unsigned SHA-256 evidence digest.
Receipt evidence APIs
Native Base USDC transfer inspection APIs with free demos, documented x402 challenges and an independently market-verified 0.01 USDC full-receipt canary.
Agent integration surfaces
MCP/A2A discovery interfaces, machine-readable catalog, OpenAPI and safety-conscious no-spend-first agent buyer guide.
Small public technical milestones, no recurring demand
Two separate operator-funded Base-mainnet x402 payment tests; not net corporate revenue or repeat demand.
Independently funded tests by a marketplace operator, not two separately qualified paying customer organizations.
Verified repeat organic buyers and qualified enterprise inquiries.
Known commercial and technical diligence questions
- Control and title: the public merchant wallet was verified by EIP-191 signature on 2026-10-14 at 05:23:10 UTC; this shows address control at that time, not legal ownership or rights to sell the project. Chain of title, sublicenses, legal ownership and asset transferability must be independently checked.
- Technical proof boundary: public RPC agreement is observational evidence. The SHA-256 digest is unsigned — not a blockchain state proof, identity certification, security audit, fraud guarantee or delivery receipt.
- Commercial proof boundary: no repeat independent customer, enterprise SLA, verified P&L, forecast, or professional valuation exists.
- Business terms: strategic license, integration or acquisition are only possible subjects for discussion. No listed price or binding offer, sale agreement, exclusivity or IP transfer without separate written owner approval and formal diligence.
Interested in technical diligence?
Start with a free, opt-in inquiry about an actual Base USDC workflow, expected evidence fields, approximate transaction volume and acceptance criteria. Do not share wallet keys, customer secrets, payment credentials or personal financial data.
Could your agents be paying twice for the same licensed result?
Review strict acceptance and exclusion rules before trialing any duplicate-work solution. No verified enterprise savings, recurring organic customers, or accepted acquisition bid. The checklist is free and nonbinding.
Read technical fit checklist ↗ · Request a free fit review ↗
Buyer diligence: deployed asset inventory
Explore the verified count and Supabase-reported deployment-bundle fingerprints for the 24 current cloud functions. This is only an engineering inventory, not evidence of source ownership, audit, transferable accounts, recurring customer revenue or agreed valuation.
View technical asset register ↗ · Machine-readable metadata ↗
Prove or disprove the need — without spending anything
We have a public, voluntary, nonbinding 14-day proposed scoping protocol for real agent-payment teams. It explicitly rules out problems already solved by ordinary retry idempotency or cache; no real customer savings are currently verified.
See proposed free buyer evaluation ↗ · Discuss a possible scoped license ↗