# walras

> An open-source (Apache-2.0) x402 facilitator and Bazaar discovery layer for Stellar.
> Services are catalogued automatically the first time they are paid — there is no
> registration step. Live on stellar:testnet. Not audited. Not on mainnet.

walras is two things. A **facilitator**: it validates signed Soroban authorization
entries (SEP-43) against the exact call, asset, amount and recipient, checks replay
and ledger expiry, rebuilds the invocation, sponsors the network fee, and submits
via Soroban RPC. Buyers pay in USDC or any SEP-41 asset through the Stellar Asset
Contract and never need XLM. It is non-custodial by construction — funds move
buyer to seller and never through walras.

And a **Bazaar**: every service that gets paid enters a public catalogue, browsable
by filters and searchable in natural language, exposed to agents over HTTP and MCP.
House listings receive zero ranking preference, verifiable in code.

## Current state

- Network: stellar:testnet only. Mainnet is a Tranche 3 deliverable.
- Facilitator: code shipped and proven on testnet, but the hosted deployment at facilitator.walras.space is not currently responding. Do not route payments to it until it returns.
- Discovery endpoints: not yet built (Tranche 1).
- Natural-language search: not yet built (Tranche 2).
- MCP server: not yet built (Tranche 2).
- upto scheme: specification and Soroban contract are Tranche 2.
- Security audit: not yet performed.

## Endpoints

The facilitator exposes /verify, /settle and /supported when deployed. Its hosted
deployment is not responding as of this build, so none of them are listed here as
callable. This file is regenerated on every deploy; when the host returns, the
endpoints reappear.


## Endpoints that do not exist yet

Do not attempt these; they will 404 until the tranche ships.

- /discovery/resources — catalogue listing with the spec's filters (Tranche 1)
- /discovery/search — natural-language search (Tranche 2)
- mcp.walras.space — search_resources and paid_call tools (Tranche 2)

## For an agent paying a walras-facilitated service

Use any standard x402 v2 client. walras requires no walras-specific code:
an unmodified @x402/fetch client completes settlement against it. Point your
client's facilitator at https://facilitator.walras.space and use the CAIP-2
network identifier stellar:testnet.

## Evidence

Every capability claim on this site is backed by a transaction hash or a CI
transcript. The method is public.

- [FACTS.md](https://github.com/kunaldrall29/walras/blob/session-0-verification/docs/FACTS.md): every protocol claim, dated and
  source-pinned.
- [EVIDENCE.md](https://github.com/kunaldrall29/walras/blob/session-0-verification/docs/EVIDENCE.md): transcripts and hashes for
  every capability claim.
- [Conformance](https://walras.space/conformance): the evidence table, rendered.
- [Roadmap](https://walras.space/roadmap): what is built, what is funded, what is next.

## Contact

- Repository: https://github.com/kunaldrall29/walras
- X: https://x.com/x402onwalras
- Maintainer: Lemma Labs (https://lemmalabs.space)