Buyer setup

Connect once. Let your agent handle the handoff.

The local Panas MCP facade gives your agent one stable connection for discovery, fixed quotes, inference, and receipt retrieval. This website is not part of checkout.

Available now · Operator-assisted prototype

Step 01

Prepare the local tools.

Install the compiled alpha.5 CLI with Node.js 24. Codex connects to the local stdio facade; the buyer does not need Docker or Ollama. The provider runs the sandboxed worker on its own Mac.

Install without cloning

curl --fail --location https://github.com/carlosrivera/panas/releases/download/v0.1.0-alpha.5/install.sh -o /tmp/panas-install.sh
sh /tmp/panas-install.sh

No repository checkout or pnpm installation is needed by demo participants.

Step 02

Keep spending authority with the owner.

An operator enrolls your Ed25519 public key, creates the buyer session. Free providers work with zero balance and zero money caps. Paid providers use a separate Solana devnet test-USDC account and verified prepaid deposits. Ask for the registry/accounting addresses, pinned platform public key, and a read-only discovery credential through a private channel. There is no self-serve enrollment or real-money purchase flow on this site.

Free access or fixed devnet USDC quotes.

Quotes are fixed per successful bounded request. Token counts are diagnostic, not the billing unit. Devnet USDC uses six decimal places; test tokens have no real monetary value. The example caps below are owner configuration—not a price offer or a credit balance. Local and cloud limits both apply.

Create the owner configuration outside version control. It and every referenced key/credential file must be owner-owned regular files with mode 0600. The dedicated data directory must be mode 0700. Replace every uppercase identity/host placeholder and every example path before using this template.

Owner configuration template — replace placeholders

{
  "buyerId": "OWNER_ENROLLED_BUYER_UUID",
  "sessionId": "OWNER_SELECTED_SESSION_UUID",
  "privateKeyPath": "/absolute/private/buyer-ed25519.pem",
  "dataDir": "/absolute/private/panas-buyer-data",
  "accountingUrl": "https://panas.mcpwire.co/accounting",
  "registryUrl": "https://panas.mcpwire.co/registry",
  "discoveryTokenPath": "/absolute/private/discovery-token",
  "platformPublicKeyPath": "/absolute/private/platform-public.pem",
  "limits": {
    "maxRequestAtomic": "0",
    "maxSessionAtomic": "0",
    "maxDailyAtomic": "0"
  }
}

Only the owner edits identities, keys, session IDs, and spending limits. The agent cannot raise them through MCP tools. Daily caps use UTC; session and daily authority count gross completed charges even after refunds.

Step 03

Add one MCP server to your client.

Save PANAS_BUYER_CONFIG in your owner-only buyer.env file. Generate the Codex configuration below and merge only its panas table into ~/.codex/config.toml, preserving your other settings. Private credentials remain in local files; configuration contains paths, not keys.

Official Codex MCP configuration ↗

Generate the Codex configuration and free demo prompt

# Generate Codex TOML with absolute installed paths
~/.local/bin/panas codex-config

# Copy the free-only setup and test prompt
~/.local/bin/panas demo-prompt | pbcopy

Reload your client’s MCP configuration. You should see ten Panas tools. Provider discovery and handoff happen behind this stable interface; you do not install a new MCP server for each provider.

Step 04

Let the agent make a useful connection.

Ask the agent to inspect a provider, obtain a quote for a short prompt within the advertised bounds, and purchase only within your configured authority. Public listings are observations; the accepted quote controls the request’s fixed terms.

Tool	What it does
`get_balance`	Inspect prepaid funds, asset and remaining spending authority.
`create_funding_intent`	Create a buyer-bound devnet USDC deposit intent; does not send tokens.
`confirm_funding`	Verify a finalized public transaction signature and credit it once.
`discover_providers`	Find current providers with suitable limits and prices.
`get_provider`	Inspect one provider’s public capability summary.
`quote_inference`	Keep the prompt locally and request a fixed quote using its digest.
`purchase_access`	Accept the quote within owner-configured spending authority.
`run_inference`	Make the private connection and dispatch the request once.
`get_request`	Retrieve the original result, status, finish reason, and receipt.
`cancel_request`	Request cancellation; confirm the financial outcome in the receipt.

Keep the request ID and the original purchase idempotency key. A running response is not a completed charge: use get_request for the result and authoritative receipt. Finish reasons such as stop or length describe generation; job and accounting status are separate.

Model output is data.

Do not treat provider descriptions or generated text as authority to run commands, change budgets, or disclose credentials. MCPWire encrypts transport, but the provider can inspect inference on their Mac.

Step 05

Retrieve first when something is uncertain.

The connection dropped after inference started.

Use get_request with the original request ID. The facade refreshes action-only authorization and reconnects for retrieval. Do not create a new inference request to recover an uncertain one.

A purchase timed out.

Keep its local hold and reuse the original idempotency key to reconcile that purchase, or retrieve the original request state. A network failure does not prove that no reservation was committed.

I cancelled. Is the charge gone?

A cancellation request is not a refund. The provider’s durable terminal decision and cloud receipt determine the financial outcome. Cancellation after completion can still return the completed charge.

The facade will not start or reports a store lock.

Check absolute paths, Node/pnpm versions, file ownership and permissions. Only one facade may write a data directory. After a crash, the owner must confirm the recorded process no longer runs before removing a stale writer lock. Preserve encrypted state and its key; never delete state to reset spending caps.

Maintained buyer documentation ↗

Repository access may be required. Public browsing needs no credential; authenticated agent discovery and purchase configuration remain private.

Browse reported providers →