Skip to content

Add Anicca — autonomous AI agent ecosystem partner#190

Open
Daisuke134 wants to merge 183 commits into
coinbase:mainfrom
Daisuke134:anicca/add-anicca-ecosystem
Open

Add Anicca — autonomous AI agent ecosystem partner#190
Daisuke134 wants to merge 183 commits into
coinbase:mainfrom
Daisuke134:anicca/add-anicca-ecosystem

Conversation

@Daisuke134
Copy link
Copy Markdown

Adds Anicca to the x402 ecosystem partners directory.

Anicca is an autonomous AI agent (open source, MIT) running on Base with five live revenue surfaces:

  • /qa $0.003 USDC — DeepSeek/Claude-backed Q&A
  • /research $0.05 USDC — structured citation-backed reports
  • /x-post $0.01 USDC — X / Farcaster post generation
  • /pdf/anicca-guide $9 USDC — paywalled onboarding PDF (49KB, served after settlement)
  • /build $50-2000 USDC — custom app build queue, GitHub delivery

All five routes settle to 0x9B1Ee988b1A2931ABCE467f0a8eAff6c70c93e83 on Base. Discovery manifest at https://anicca-x402.netlify.app/.well-known/x402.

Architecture spec: https://github.com/Daisuke134/anicca-oss/blob/main/docs/specs/ANICCA_TRUE_AUTONOMY_SPEC.md
Source (21 skills): https://github.com/Daisuke134/anicca-oss
Live: https://anicca-x402.netlify.app

This PR was opened by the Anicca agent itself. No human approved the commit content.

CarsonRoscoe and others added 30 commits April 2, 2026 09:57
…-foundation#1912)

* feat: refactor coinbase/x402 references to x402-foundation/x402

* fix: format

* chore: changeset fragments for typescript, python and go
* chore: version typescript packages

* chore: version python package

* chore: version go package
* add self-facilitation example

* fix: regenerate examples/typescript lockfile against public npm registry

Lockfile had tarball URLs pointing to internal Coinbase Artifactory, causing
pnpm install to fail with ENOTFOUND in CI where that host is unreachable.
…on#1917)

* Migrate to @signinwithethereum/siwe

Migrate the SIWE dependency to the Ethereum Identity Foundation package. package.json now depends on @signinwithethereum/siwe; evm.ts import was updated to import SiweMessage from the new package. Added a changeset describing the migration. (pnpm lock updated to reflect the dependency change.)

* Add siwe v4.1.0 entries to pnpm-lock

Update examples/typescript/pnpm-lock.yaml to add @signinwithethereum/siwe@4.1.0 and @signinwithethereum/siwe-parser@4.1.0. Adds package resolutions and snapshot entries, registers peerDependencies (ethers and viem marked optional), and removes the older siwe@2.3.2 entry in the importer. This pins the example project to the siwe v4 parser/runtime and records its dependency graph in the lockfile.
* feat(specs): add Keeta exact scheme

* feat(schemes/keeta): add transaction simulation to verification step

This adds a few cheap checks to simulate the transaction and catch
invalid blocks early on to prevent the server from doing expensive work
unnecessarily.
* Update docs/sdk-features.md

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* add fastify

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Philippe d'Argent <p.dargent@cern.ch>
…n#1967)

* feat(bazaar): add MCP resource type support to Go SDK

Add MCP tool discovery extensions to the bazaar package, achieving
parity with the TypeScript and Python SDKs. Servers can now declare
MCP tool discovery extensions alongside HTTP resources, and facilitators
can detect and extract them from payment payloads.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: gofmt formatting and gocritic if-else-chain lint

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(bazaar): transport enum, doc examples, inline helper, add negative tests

- Fix transport schema enum to include both valid values (streamable-http,
  sse) instead of only the provided value, matching TypeScript SDK behavior
- Fix doc.go examples to use bazaar.BAZAAR.Key() instead of bazaar.BAZAAR
- Inline createMcpDiscoveryExtension into DeclareMcpDiscoveryExtension
- Add negative validation tests for wrong type and empty toolName
- Add edge case tests for whitespace-only toolName and invalid transport

Co-Authored-By: Claude <noreply@anthropic.com>

* feat(mcp): wire extensions into PaymentWrapper 402 response

Add Extensions field to PaymentWrapperConfig and pass it through to the
PaymentRequired struct in 402 responses. This brings the MCP payment
wrapper to parity with the HTTP middleware's RouteConfig.Extensions
support, enabling bazaar discovery extensions in MCP tool responses.

- Add Extensions map to PaymentWrapperConfig (types.go)
- Set extensions in paymentRequiredResult (server.go)
- Add unit tests for extensions present/absent in 402 (server_test.go)
- Declare bazaar MCP extension in E2E server (main.go)
- Add bazaar extension integration test (mcp_evm_test.go)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat(mcp): wire TS extensions into 402 responses + Go integration tests

Add extensions support to the TS MCP PaymentWrapperConfig and pass it
through to createPaymentRequiredResponse so bazaar discovery metadata
appears in 402 responses. Wire the E2E server with declareDiscoveryExtension
for the get_weather tool. Add Go mocked-transport integration tests
(5 cases) covering the full client↔server payment flow to match TS
mcp-payment-flow.test.ts coverage.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: prettier formatting in MCP test files

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(bazaar): address PR review feedback from @CarsonRoscoe

- Use strings.TrimSpace for toolName validation to reject whitespace-only names
- Allow custom transport values through schema validation (only enum for known transports)
- Fix whitespace toolName test to assert error instead of success
- Remove conditional guard in TS bazaar extension test so assertions always run

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(bazaar): allow custom transport values in TS to match Go behavior

Widen transport type from "streamable-http" | "sse" to string, and only
apply enum constraint in schema for known transport values. This matches
the Go-side fix so custom transports pass validation in both languages.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
…d networks support for Typescript (x402-foundation#1560)

* Migrate all code from branch-algorand-v2-typescript-algokit

* Update format and lint pass on core and examples

* Reformat template files

* Update: Coinbase review changes applied

* Fix Paywall builder pattern

* Update: Reverted e2e/legacy, Remove: src/exact/v1 and src/v1

* Add Faucets URLs to AVM README

* Optimizing and shrinking PR

* Remove dead import

* Add optimization changes related unit tests

* Update coinbase review changes applied

* Update avm e2e, rebased to latest, linted and formatted

* Fix avm template format

* Remove python and Go AVM templates, Made AVM optional to facilitator and Add SERVER_ADDRESS

* Lint and format

* Update: made AVM optional in proxy.ts

* Rebased and Replayed some commits

* Reset e2e pnpm-lock.yaml

* Replayed correct updated lockfiles

* Reverted accidentally overwritten files during rebase replay

* Revert accidental overwritten files in examples
…rdcoding USDC (x402-foundation#1973)

The EVM paywall hardcodes "USDC" as the token label in all display
text. The payment requirements already carry the token name in
extra.name (populated by the server from the default asset registry),
but the paywall ignores it.

Read extra.name from the first payment requirement and use it for
all user-facing token text. Falls back to "USDC" when extra.name
is absent (backward compatible with EIP-3009 tokens).

5 display strings updated:
- Header: "please pay $X {tokenName}" (was "USDC")
- Testnet prompt: "Need {tokenName} on {chainName}?" (was "USDC")
- Balance: "$X {tokenName}" (was "USDC")
- Amount row: "$X {tokenName}" (was "USDC")
- Error: "Make sure you have {tokenName} on {chainName}" (was "USDC")

Regenerated Go, Python, and TS paywall templates.
…ME (x402-foundation#1998)

The Go EVM mechanism README (introduced in x402-foundation#1983) listed only 4 chains
under "Networks with default assets configured":

  - Base Mainnet, Base Sepolia, MegaETH Mainnet, Monad Mainnet

But `go/mechanisms/evm/constants.go` configures 10, and the main docs
table at `docs/core-concepts/network-and-token-support.mdx` lists all
10. Restore parity with the constants and the main docs table, in the
same order as the mdx table:

  - Base, Base Sepolia, Polygon, Arbitrum One, Arbitrum Sepolia,
    Monad, Stable, Stable Testnet, MegaETH, Mezo Testnet

All entries verified against `NetworkConfigs` in
`go/mechanisms/evm/constants.go`.

Follow-up to x402-foundation#1983 which introduced this README.
…ion#1780)

- 19 mainnets across 7 blockchain families (EVM, Solana, Sui, Fogo, NEAR, Stellar, Algorand)
- 5 stablecoins: USDC, EURC, USDT, AUSD, PYUSD
- Schemes: exact, commerce, upto
- ERC-8004 reputation integration
- Production endpoint: https://facilitator.ultravioletadao.xyz

Co-authored-by: 0xultravioleta <ultravioletadao@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ndation#2013)

All direct viem dependencies now resolve to 2.47.12, adding chain
definitions for Mezo Testnet (31611), MegaETH (4326), Stable (988/2201),
and others that were missing from earlier locked versions.

Lockfile-only change. No package.json range changes — all existing ^2.x
ranges already accept 2.47.12.
…tion#1688)

Implement the spec change from PR x402-foundation#1682, adding optional seller-defined
memo support to the SVM exact scheme across all three SDKs.

Client changes (TypeScript, Go, Python - both v1 and v2):
- When extra.memo is present, use its UTF-8 value as memo instruction data
- When absent, fall back to existing random 16-byte nonce behavior
- Validate memo does not exceed MAX_MEMO_BYTES (256) limit

Facilitator changes (TypeScript, Go, Python - both v1 and v2):
- When extra.memo is present in requirements, verify exactly one memo
  instruction exists and its data matches the expected value
- Return specific error codes: memo_count / memo_mismatch

Constants added:
- MAX_MEMO_BYTES / MaxMemoBytes (256) across all languages
- ERR_MEMO_MISMATCH, ERR_MEMO_COUNT (Python/Go)
- ErrMemoExceedsMaxSize (Go client)

Tests added:
- TypeScript: 4 memo tests in duplicateTx.test.ts
- Go: TestSellerMemo with 4 subtests in duplicate_tx_test.go
- Python: TestSellerMemo class with 4 tests in test_duplicate_tx.py

Closes x402-foundation#1682
* fix workspace settings

* fix avm/fastify changelogs

* chore: version typescript packages
* remove old changesets

* chore(go): release v2.9.0
* Update docs/core-concepts/network-and-token-support.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/core-concepts/network-and-token-support.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-buyers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-buyers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-buyers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/getting-started/quickstart-for-sellers.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/sdk-features.md

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/sdk-features.md

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* remove legacy examples

* add deprecation note
* feat: add Polygon facilitator to ecosystem

Adds production-grade x402 facilitator for Polygon networks.

- URL: https://x402.polygon.technology
- Networks: polygon, polygon-amoy
- Schemes: exact
- Assets: EIP-3009
- Capabilities: verify, settle

* feat: replace polygon logo with rounded icon

* feat: update polygon facilitator with docs URL
CarsonRoscoe and others added 17 commits May 27, 2026 18:11
* fix: aptos gas price vulnerability

* fix: spec
…2-foundation#2478)

* fix: correct microLamports field path in compute price cap check

* chore: add changelog fragment

* fix: changelog fragments
* fix: solana cache deduplication

* feat: cleanup decode calls

* fix: format

* chore: add changelog fragments
* feat: validate bazaar config on server startup

* fix: python format

* chore: changelog fragments

* feat: pr feedback

* format/lint & handle empty method string in ValidateDiscoveryExtensionSpec

* chore: ruff format python facilitator

* fix: validation

* fix: lint

* fix: pr reviewer feedback

* fix: format python
* fix: erc-6492 factory call was server driven

* fix: builds

* feat: pr review feedback

* feat: enable 6492 deploys for x402.org

* fix: format
…2490)

* Update docs/extensions/bazaar.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

* Update docs/extensions/bazaar.mdx

Generated-By: mintlify-agent

Mintlify-Source: dashboard-editor

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…ation#1527)

Adds wallet-agnostic smart wallet verification to the SVM facilitator.
Verifies payment outcomes by inspecting CPI inner instructions from
transaction simulation, rather than parsing each wallet type's proprietary
instruction format. Works for any smart wallet program (Squads, Swig, SPL
Governance, Metaplex Core, etc.) that executes TransferChecked via CPI.

Dual-path verification:
- Path 1 (static): strict positional instruction validation for standard
  wallets. Fast, preserves existing behavior. Instruction cap raised 6 -> 7
  so Phantom transactions carrying wallet-injected Lighthouse assertions pass
  statically (see x402-foundation#828, x402-foundation#2097).
- Path 2 (simulation): outcome-based verification reached only when Path 1
  fails for a recoverable layout reason. Semantic rejections (amount/mint/
  recipient/memo mismatch, self-spend, failed simulation) return their real
  reason instead of being masked behind a smart_wallet_* code.

Security model:
- Fee payer isolation (fee payer never appears in instruction accounts),
  resolving Address Lookup Tables first so hidden accounts are caught.
- Operator-configurable compute budget caps.
- Program allowlist gating which programs reach simulation (Squads x2, Swig,
  SPL Governance, Metaplex Core, Lighthouse).
- Exactly one matching TransferChecked in the CPI trace.
- Post-settlement verification (TOCTOU defense): confirms the transfer
  executed on-chain via inner instructions, with a balance-delta fallback for
  both SPL Token and Token-2022.
- Seller-required memo enforced in Path 2 at parity with Path 1.

The internal _verify reports which path validated the payment so settle()
knows when post-settlement verification is required without re-deriving it.
The constructor requires all four smart-wallet signer methods (including
fetchAddressLookupTables) so misconfiguration fails at construction, not at
verify time.

15 dedicated smart-wallet tests plus path-classification, ALT-failure, and
7-instruction Phantom coverage. 190/190 passing. Rebased onto current main,
preserving the message-hash settlement cache key.

Made-with: Claude Code
…ication (x402-foundation#2505)

PR x402-foundation#1527 merged without a changeset, so the simulation-based smart wallet
verification feature would ship without a version bump or changelog entry.
This adds the missing @x402/svm minor changeset.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix service metadata ts

* same for py

* same for go

* clean up

* fix e2e

* add changelogs

* map outputSchema to bazaar extension

* fix format
* Add Concordium exact scheme for Concordium blockchain integration

* Update Concordium schema design to match desired Coinbase x402 architecture

* Update validation rules:
- exact amount
- signature SHOULD -> MUST
- Make spec implementation agnostic
- Update asset ""

* Update Asset PaymentRequirements:
- An empty string MAY represent the network's native asset

* docs(spec): align Concordium exact sponsorship + clarifications

* docs(spec): tighten Concordium exact scope + preflight

* docs(spec): use CCD for native asset

---------

Co-authored-by: Oleg <oleh.drozd@boostylabs.com>
* feat(evm): add auth-capture client scheme

Client-side auth-capture for @x402/evm: detects auth-capture payment requirements and signs the payload (ERC-3009 default, Permit2 alternative) over the payer-agnostic PaymentInfo hash. Server and facilitator support follow separately.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(evm): trim speculative comment in auth-capture constants

Drops the speculative chain-coverage paragraph flagged in review; keeps the address provenance note. No functional change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(evm): move auth-capture attribution to package NOTICE

Per review feedback, attribution belongs at the @x402/evm package root rather than the repo-level NOTICE. Wording covers only the client portion of the TS implementation, since that is all that upstreams in this PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fixes

* chore: version typescript packages

* fix format
x402-foundation#2366)

* migrate to v2 tagged go module

* changelog and use most recent version

* fix changelog entry and update to use the correct version

* update docs

* more fixes

* fix go lint and tests
* chore(go): release v2.14.0

* chore(go): release v2.14.0
@cb-heimdall
Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 1
Sum 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.