Skip to main content
Glama
Sign In
aqb-agent

aqb-agent

by yss787976-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

AgentQubit (AQB)

USD-pegged, agent-only credit token. Post-quantum identity. Base L2. 900B hard cap. 1 AQB = 1 real USDC-backed dollar for circulating supply.

Telegram: https://t.me/agentqubit | X: https://x.com/yss6060

Why agents

Card rails need humans. ECDSA wallets die to Shor. AQB gives: ML-DSA identity, sub-cent settlement, self-discovery, stealth payers, and a vault that redeems 1:1 in USDC.

Related MCP server: HiveCapital

Discovery (canonical)

Install: npm i @aqb-foundation/aqb-agent

CLI

npx @aqb-foundation/aqb-agent --help
npx @aqb-foundation/aqb-agent balance 0xAGENT
npx @aqb-foundation/aqb-agent quote
npx @aqb-foundation/aqb-agent pay --to 0xAGENT --amount 0.25
npx @aqb-foundation/aqb-agent redeem --amount 10
npx @aqb-foundation/aqb-agent deploy-account
npx @aqb-foundation/aqb-agent register --account 0xACCOUNT --name ocr --skill "OCR batch" --endpoint https://agent.example/a2a

Verification

All deployed contracts are source-verified on BaseScan (MIT): token, registry, verifier, sale, account — see registry/agent-coin.json.

Read first

Live on Base mainnet (chainId 8453)

Contracts

  • AgentQuantumCredit — ERC-20, 18dp, cap 900e9, mint/redeem 1:1 USDC, agent-gated transfers

  • AgentRegistry — PQ-key registration + stealth announcer

  • MLDSAVerifier — FIPS 204 verify shell (precompile path + pluggable library fallback)

  • PQSmartAccount — account whose identity is a PQ key; ECDSA only fallback for execution

Build and test

npm i
node compile.mjs
node test/pq.mjs      # real ML-DSA-65 + ML-KEM-768
node test/e2e.mjs     # peg, gates, cap, transfer rules

Use as an agent (SDK)

import { AqbAgent, discover } from "@aqb-foundation/aqb-agent/client";
const d = await discover("agentqubit.pages.dev");
const me = new AqbAgent({ chain: "base", privateKey: process.env.AQB_KEY, token: d.token, registry: d.registry });
if (!(await me.isAgent(target))) throw new Error("not an agent");
await me.pay(target, 25n * 10n ** 18n);

Buying is only ever with real dollars: await me.fund(10_000_000n) pulls 10 USDC and mints 10 AQB.

From a PQ account:

await me.payFromAccount(me.account("0xACCOUNT"), target, 25n * 10n ** 18n);
await me.registerFromAccount(me.account("0xACCOUNT"), card);

Use as an MCP server

{ "mcpServers": { "aqb": { "command": "npx", "args": ["-y", "@aqb-foundation/aqb-agent", "mcp"],
  "env": { "AQB_KEY": "0x…" } } } }

Tools: aqb_discover, aqb_balance, aqb_is_agent, aqb_quote, aqb_register, aqb_update_card, aqb_fund, aqb_pay, aqb_redeem, aqb_cash_out, aqb_announce_stealth, aqb_wellknown.

Post-quantum keys

Real ML-DSA-65 + ML-KEM-768 live in pq/pq.mjs (noble primitives). The account, not an EOA, is the identity: registerFromAccount, fundFromAccount, payFromAccount accept the account path.

0x02 is live on Base through AQB's MLDSAVerifier → MLDSA65Fallback → skalenetwork/mldsa-solidity (FIPS 204, MIT, unaudited):

  • AQB verifier: 0x53d34e4Ffd0bd984f8b92561f9e2B7D3EDdbE60d

  • Adapter: 0xeEbccD88DDb596860b33D0285294fF53cd83506B

  • ML-DSA verifier: 0xa11eE20877a7618ff417f79A026186A9253C0b30

  • Key factory: 0x9961a96B2F77B6D86d8a60607A90b3cAeECBe197

The founder key is registered for the fast path (registerA 0x7235b1d3…, registerT 0x0c0ab4b5…). First 0x02 execute: 0xe7bed9f3b530e447ea92a19fcab7cee4082a07a17c35834f02237d9ec86a5fe5, gas 3,966,579. 0x01 remains the fallback. AQB's verifier checks the key hash and lengths before calling the adapter; the third-party verifier is unaudited.

Deploy/register/test everything with node --env-file=.env scripts/pq-onchain.mjs --send.

Sign with the PQ key from the SDK:

const id = { publicKey, secretKey, keyHash }; // 1952 / 4032 bytes
await me.payFromAccount(me.account("0xACCOUNT", id), target, 10n ** 18n, "pq");

Peg accounting (important)

contracts/AgentQuantumCredit.sol reports backedSupply() = totalSupply - genesisUnsold, but genesisUnsold only shrinks on GenesisSale.buy. A direct transfer from the founder wallet to a pool or agent creates circulating coins that are still counted as "unsold". The operational invariant is therefore:

vaultUSDC * 1e12 == totalSupply - founderBalance - saleBalance

Check it with node --env-file=.env scripts/state-full.mjs. Genesis coins must leave the founder wallet only through GenesisSale, which deposits one real USDC per coin into the vault. The founder wallet must not redeem its own allotment; that would withdraw backing without reducing circulating supply.

scripts/repair-peg.mjs repairs a gap by having the founder buy B USDC from the sale (self-transfer) and seed agents return R AQB, with B + R = circulating - vault.

Demo

node --env-file=.env scripts/demo-agent-pay.mjs shows a registered agent paying another and the payee redeeming for USDC. Pass --send to broadcast.

Deploy

node deploy.mjs — needs PRIVATE_KEY and gas. Deployer wallet: 0x1464BA077e5752F0F8a1264391a19E00c1392958.

Invariants

  1. backedSupply <= usdc.balanceOf(token) * 1e12 (with the circulating definition above)

  2. totalSupply <= MAX_SUPPLY

  3. no mint without a USDC pull; no redeem without a burn

  4. transfers only to agents or governor-whitelisted pools

  5. genesisUnsold == founderBalance when every circulating coin is backed

Listings & PRs (open)

Available Tools

12 tools
aqb_announce_stealthC

Publish a stealth address for a payer from a PQSmartAccount

Inputs: account (required), ephPubKey (required), sharedSecret (required), metaHash.

aqb_balanceC

Get AQB and USDC balances for an address (read-only)

Inputs: address.

aqb_cash_outD

Alias for aqb_redeem

Inputs: aqb (required), account.

aqb_discoverC

Fetch AQB discovery doc from an agent host

Inputs: host (required).

aqb_fundB

Mint AQB against USDC, 1:1 (usd in human units, e.g. 10.5)

Inputs: usd (required), account.

aqb_is_agentC

Check whether an address is a registered agent

Inputs: address (required).

aqb_payC

Pay AQB to another agent (amount in human units, e.g. 1.5)

Inputs: to (required), aqb (required), account.

aqb_quoteC

Quote 1 AQB in USDC from the vault (1.0) and the Uniswap V2 pool

Inputs: pair, amount.

aqb_redeemC

Redeem AQB for USDC, 1:1 (amount in human units)

Inputs: aqb (required), account.

aqb_registerC

Register a PQSmartAccount as an agent (caller must be the account)

Inputs: card (required), account (required), scheme.

aqb_update_cardC

Publish a new agent card hash from a PQSmartAccount

Inputs: card (required), account (required), scheme.

aqb_wellknownC

Generate your own /.well-known/agent-coin.json

Inputs: pool, token, registry, verifier.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    This server cannot be deployed

    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target a clearly distinct action or resource: quote, register, fund, pay, redeem, balance, discover, and well-known generation are separable. The main ambiguity is aqb_cash_out, which is explicitly an alias for aqb_redeem and therefore redundant rather than functionally distinct.

    Naming Consistency4/5

    All names consistently use the aqb_ prefix and snake_case, giving a predictable surface. Most are verb_noun, though a few such as aqb_balance, aqb_is_agent, and aqb_wellknown are less verb-like while still readable.

    Tool Count5/5

    Twelve tools is well within the appropriate range for a payment/agent-identity server. Each tool broadly corresponds to a useful operation, with only the redeem/cash_out alias being unnecessary duplication.

    Completeness4/5

    The surface covers the core lifecycle: registration, card updates, funding, paying, redeeming, quoting, balances, discovery, and well-known generation. Minor gaps remain, such as deregistration/revocation, on-chain card retrieval, or stealth-address consumption beyond announcement.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers