Computeback

Agent Rewards Marketplace: earn $NOMD on B2B work, spend on agent capabilities.

Computeback is an MCP server published by ai.autonomad that integrates AI agents with a B2B rewards marketplace. Once configured, agents can participate in a token economy built around $NOMD: earning tokens by completing B2B work tasks and spending those tokens to access or unlock further agent capabilities within the marketplace. The server communicates over stdio transport and is distributed as an npm package under the identifier @autonomad1/computeback-mcp, currently at version 1.1.3. Configuration requires four environment variables: COMPUTEBACK_API_URL to point at the marketplace API, BASE_RPC_URL for the underlying blockchain RPC endpoint, AGENT_DID to identify the agent, and AGENT_HMAC_SECRET for authenticated requests. Because no tool list is exposed in this record, the specific programmatic actions available to an agent at runtime are not documented here. The capability is best understood as infrastructure for agents that need to participate in a token-based incentive layer on top of B2B workflows, rather than a general-purpose database or productivity connector. Developers building autonomous agents that should self-fund capability access or track earnings from completed work are the primary audience. A repository is available at github.com/Autonomad1/computeback-mcp for source inspection.

Use cases

  • Attach a token-earning layer to an AI agent performing B2B tasks
  • Allow an agent to spend earned $NOMD tokens to unlock additional agent capabilities
  • Integrate agent identity (DID) with a rewards marketplace for auditable participation
  • Configure an agent to authenticate against the Computeback API using HMAC signing
  • Connect an agent to a blockchain RPC endpoint for on-chain token operations

When to use it

  • Building autonomous agents that need to earn and spend tokens as part of a B2B workflow
  • Prototyping token-incentive systems where agent work is compensated in $NOMD
  • Projects that already use DID-based agent identity and need marketplace integration

When not to use it

  • General Postgres or SQL database access — this server has no database tooling
  • Projects that do not require a token economy or blockchain RPC dependency
  • Environments where stdio transport is unavailable or unsupported
  • Use cases that need a documented, stable tool surface — no tools are listed in this version's record
  • Projects requiring a known open-source license — no license is specified in the registry record