Ausca

MCP serverAI & models

agent-services gives your AI access to pay-per-call APIs without needing accounts or keys. Your AI can use the services it needs, pay only for the calls it makes, and get a verifiable receipt for each one. It is community-built, with code available on GitHub.

Available today. Use it from your connected AI after setup.

After adding it, your AI can start calling the available pay-per-call APIs right away. There is no account or key setup to do first.

Then ask your AI: use the ausca agent inbox attachment tool from Ausca

What your AI can do with it

  • Call paid APIs and pay only for what is used
  • Use services without creating an account
  • Make calls without setting up or storing API keys
  • Get a verifiable receipt for every call

From the project's README

As published by auscahq/ausca in README.md.

Agents buy infrastructure the way they call tools: send the request, pay the 402 challenge within a hard USD cap you set, read the result and its settlement proof. The catalog, prices, and schemas are immutable and public at ausca.com/catalog.json; the full agent contract is ausca.com/SKILL.md.

Services and prices

ServiceWhat it doesPrice (USD)
Document OCRNormalized text with line confidence from one committed document$0.25 per document
Document AnalysisNormalized forms, tables, signatures, or layout from one committed document$0.30 to $0.75, sized by document bytes
Media TranscriptionNormalized transcript of one committed audio or video file$0.40 to $1.30, sized by media bytes
Browser SessionRemote browser with standard CDP access$0.05 / 10 min, $0.10 / 30 min, $0.20 / 60 min
Agent InboxA renewable receive-only email address your agent owns$0.05 / hour, $0.20 / day, $1.00 / week
Inbox ExtensionAdd time to an active inbox without changing its address$0.05 / hour, $0.20 / day, $1.00 / week

Prices are the public catalog values at the time of writing; the live catalog is authoritative.

Use it in 60 seconds

MCP (Claude Desktop, Cursor, any MCP host): the local server holds your wallet and pays within your cap. Tools are derived from the live catalog.

{
  "mcpServers": {
    "ausca": {
      "command": "npx",
      "args": ["-y", "ausca", "mcp"],
      "env": {
        "AUSCA_PRIVATE_KEY": "0x...",
        "AUSCA_MAX_PAYMENT_USD": "0.50"
      }
    }
  }
}

TypeScript

import { AuscaClient } from "ausca";

const client = AuscaClient.withLocalKey({
  privateKey: process.env.AUSCA_PRIVATE_KEY, // pays USDC on Base
  maxPaymentUsd: 0.5,                        // hard per-call cap
});

const outcome = await client.invoke("browser.session", { duration_seconds: 600 });
console.log(outcome.result, outcome.payment?.transaction);

CLI

npx ausca catalog
npx ausca price document.ocr
AUSCA_PRIVATE_KEY=0x... AUSCA_MAX_PAYMENT_USD=0.50 \
  npx ausca invoke browser.session '{"duration_seconds":600}'

Python

pip install ausca
from ausca import AuscaClient

client = AuscaClient.with_local_key(private_key=key, max_payment_usd=0.50)
outcome = client.invoke("browser.session", {"duration_seconds": 600})

A remote MCP server also runs at https://ausca.com/mcp (Streamable HTTP) for discovery, preparation, and state reads; payment always signs on your side, which is why the local server exists.

How payment works

Every service is an x402 v2 payable resource. An unsigned request returns the exact payment requirement; the client pays it only if it fits your cap, then retries the same bytes with the same idempotency key, so an uncertain retry can never buy twice. Settlement is USDC on Base and every completed invocation carries a receipt with a public, hash-only verification page. Payment rails are pluggable behind one interface; the official @x402/* libraries do all signing.

Document and media services take an immutable artifact commitment instead of raw bytes: npx ausca commit file.pdf uploads through the keyless ingress and returns the commitment the offer input carries.

What is in this repository

PackageRegistryWhat it is
auscanpmThe front door: library, CLI, and local MCP server
@ausca/sdknpmThe typed engine: client, payment authorities, artifact store
auscaPyPIPython client and CLI with the same ports
@ausca/ai-sdknpmVercel AI SDK tools for any x402 v2 resource
langchain-auscanpmLangChain tools for any x402 v2 resource
skills/ausca.comAgent skills, mirrored from the live origin

The service runtime is not in this repository; this is the complete public buyer side. server.json carries the official MCP registry identity com.ausca/agent-services.

Links

License

MIT

Tools it offers (14)

What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • ausca_agent_inbox_attachment
  • ausca_agent_inbox_delete
  • ausca_agent_inbox_messages
  • ausca_agent_inbox_read
  • ausca_agent_inbox_status
  • ausca_artifact_access
  • ausca_browser_session_close
  • ausca_browser_session_connect
  • ausca_browser_session_status
  • ausca_cancel_invocation
  • ausca_get_invocation
  • ausca_get_offer
  • ausca_prepare_invocation
  • ausca_search_offers

Signals

Last commit
Sep 2026
Weekly downloads
63

ahel review (caution)

  • S2medium
    demands high-sensitivity credentials

Automated review, not a security audit. Ruleset v1.

Advanced
Delivery
agent-services MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
com-ausca-agent-services
Source
github.com/auscahq/ausca
Hosted endpoint
https://ausca.com/mcp