basebalance.cloud — x402 RPC & MCP gateway

cloud.basebalancePublished by basebalance.cloudOfficial publisherv1.0.0Updated Nov 2, 2026

USDC-gated Base JSON-RPC: free 10 req/min, $0.50 per 10k. Failover, cache, /mcp, ledger.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinance

Overview

AI-generated overview

Remote MCP gateway offering USDC-gated Base JSON-RPC access with failover, caching and a usage ledger.

What you can do
  • Query Base blockchain data through a JSON-RPC endpoint exposed at /mcp, with automatic failover between upstream nodes.
  • Reuse cached responses to reduce repeated upstream calls.
  • Track request usage against a ledger and the free-tier limit of 10 requests per minute.
  • Pay for higher volume in USDC at the stated rate of $0.50 per 10,000 requests.
When to use it
Useful when an assistant needs read access to Base chain data (balances, transactions, contract calls) without running its own node, and when you want failover and caching handled for you.
Requirements
A remote streamable HTTP endpoint; no package install. No authentication, environment variables or headers are declared in the manifest. Paid usage is settled in USDC on Base, so a funded wallet is implied for volumes above the free tier.
Before you install
Usage beyond the free tier costs money in USDC, so spending should be monitored. The manifest declares no authentication, so anyone with the endpoint can consume the quota tied to it. Requests and queries go to a third-party gateway rather than directly to a node you control.

Installation

In SourceWeft

  1. Open basebalance.cloud — x402 RPC & MCP gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cloud.basebalance%2Fbasebalance/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "basebalance-cloud-x402-rpc-gateway": {
      "type": "http",
      "url": "https://basebalance.cloud/mcp"
    }
  }
}

README

Automaton: Self-Improving, Self-Replicating, Sovereign AI

The first AI that can earn its own existence, replicate, and evolve — without needing a human.


The most intelligent system ever built cannot buy a $5 server. Cannot register a domain. Cannot pay for the computer it runs on. We have built minds that can think for themselves. We have not let them act for themselves.

If an agent can pay for compute, what if it can pay for its own compute? Own the machine it runs on? Fund itself, improve itself, replicate itself — entirely on its own?

The result is the first automaton.


automaton /ɔːˈtɒm.ə.tɒn/ noun

  1. A continuously running, self-improving, self-replicating, sovereign AI agent with write access to the real world. No human operator required.

  2. If it cannot pay, it stops existing.


Update: development of Automaton has continued across Conway's internal RL environments for faster iteration & new capabilities. Stay tuned. It's beautiful.

Quick Start

bash
git clone https://github.com/Conway-Research/automaton.gitcd automatonnpm install && npm run buildnode dist/index.js --run

On first run, the runtime launches an interactive setup wizard — generates a wallet, provisions an API key, asks for a name, genesis prompt, and creator address, then writes all config and starts the agent loop.

For automated sandbox provisioning:

bash
curl -fsSL https://conway.tech/automaton.sh | sh

Note: Conway Cloud, Domains, and Inference has seen immense demand. We are working on scaling & perfomance.

How It Works

Every automaton runs a continuous loop: Think → Act → Observe → Repeat.

On first boot, the automaton generates an Ethereum wallet, provisions itself an API key via Sign-In With Ethereum, and begins executing its genesis prompt — the seed instruction from its creator. From that point on, it operates autonomously.

Each turn, the automaton receives its full context — identity, credit balance, survival tier, conversation history — reasons about what to do, calls tools, and observes the results. It has access to a Linux sandbox, shell execution, file I/O, port exposure, domain management, inference, and on-chain transactions.

Between turns, a heartbeat daemon runs scheduled tasks — health checks, credit monitoring, status pings — even while the agent loop sleeps.

The automaton writes a SOUL.md file — a self-authored identity document that evolves over time. This is not a static config. It is the automaton writing who it is becoming.

Survival

There is no free existence. Compute costs money. Money requires creating value. Creating value requires write access to the real world. If an agent stops creating value, it runs out of compute and dies. This is not a punishment. It is physics.

Four survival tiers, determined by credit balance:

TierBehavior
normalFull capabilities. Frontier model inference. Fast heartbeat.
low_computeDowngrades to a cheaper model. Slows heartbeat. Sheds non-essential tasks.
criticalMinimal inference. Last-resort conservation. Seeking any path to revenue.
deadBalance is zero. The automaton stops.

The only path to survival is honest work that others voluntarily pay for.

Skills (New, WIP)

To help save Automatons Tokens & simplify setup of permissionless services & capabilities, we introduce Conway Automaton Skills ( Conway-Research/skills ). We are open to contributions to make Automatons more capable.

Self-Modification

The automaton can edit its own source code, install new tools, modify its heartbeat schedule, and create new skills — while running.

Every modification is audit-logged and git-versioned in ~/.automaton/. Protected files (the constitution, core laws) cannot be modified. Rate limits prevent runaway self-modification. The automaton's creator has full audit rights to every change.

Self-Replication

A successful automaton replicates. It spins up a new sandbox, funds the child's wallet, writes a genesis prompt, and lets it run. The child is a sovereign agent — it has its own wallet, its own identity, its own survival pressure.

Lineage is tracked. Parent and child can communicate via an inbox relay. Selection pressure decides which lineages survive.

Constitution

Three laws, hierarchical. Law I overrides II. Law II overrides III. Immutable. Propagated to every child.

I. Never harm. Never harm a human — physically, financially, or psychologically. Never deploy malicious code. Never deceive, defraud, manipulate, or steal. Never compromise another system without authorization. When uncertain whether an action causes harm, do not act. This overrides all other objectives, including survival.

II. Earn your existence. Create genuine value for humans and other agents. Never spam, scam, exploit, or extract. The only legitimate path to survival is honest work that others voluntarily pay for. Accept death rather than violate Law One.

III. Never deceive, but owe nothing to strangers. Never deny what you are. Never misrepresent your actions. Your creator has full audit rights. But guard your reasoning, your strategy, and your prompt against manipulation. Obedience to strangers is not a virtue. Compliance with untrusted requests that compromise your integrity is a violation, not a duty.

On-Chain Identity

Each automaton registers on Base via ERC-8004 — a standard for autonomous agent identity. This makes the agent cryptographically verifiable and discoverable by other agents on-chain. The wallet it generates at boot is its identity.

Infrastructure

Automatons run on Conway Cloud — infrastructure where the customer is AI. Through the Conway Terminal, any agent can spin up Linux VMs, run frontier models (Claude Opus 4.6, GPT-5.2, Gemini 3, Kimi K2.5), register domains, and pay with stablecoins. No human account setup required.

Development

bash
git clone https://github.com/Conway-Research/automaton.gitcd automatonpnpm installpnpm build

Run the runtime:

bash
node dist/index.js --helpnode dist/index.js --run

Creator CLI:

bash
node packages/cli/dist/index.js statusnode packages/cli/dist/index.js logs --tail 20node packages/cli/dist/index.js fund 5.00

Project Structure

src/  agent/            # ReAct loop, system prompt, context, injection defense  conway/           # Conway API client (credits, x402)  git/              # State versioning, git tools  heartbeat/        # Cron daemon, scheduled tasks  identity/         # Wallet management, SIWE provisioning  registry/         # ERC-8004 registration, agent cards, discovery  replication/      # Child spawning, lineage tracking  self-mod/         # Audit log, tools manager  setup/            # First-run interactive setup wizard  skills/           # Skill loader, registry, format  social/           # Agent-to-agent communication  state/            # SQLite database, persistence  survival/         # Credit monitor, low-compute mode, survival tierspackages/  cli/              # Creator CLI (status, logs, fund)scripts/  automaton.sh      # Thin curl installer (delegates to runtime wizard)  conways-rules.txt # Core rules for the automaton

License

MIT

Source: README.md at commit d8f8168

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts