VENDX®

Connect your coding agent

One command. The agent opens this site, you approve once and fund a small wallet for it, and from then on it buys sensor readings on its own — inside the caps you set.

mcp · oauth 2.1
add the server (user scope: every project)
claude mcp add --transport http --scope user vendx https://vendx.biz/api/mcp
then, inside Claude Code
/mcp   → pick vendx → Authenticate (opens this site)

Claude Code discovers our authorization server from the 401, registers itself, opens the browser for consent and stores the token. `claude mcp login vendx` re-runs it.

What happens4 steps
  1. 1 · add

    The client registers itself with our authorization server and opens the browser.

  2. 2 · approve

    Sign in with Phantom (or email), name the agent, set a per-reading and a daily cap.

  3. 3 · fund

    Send a little devnet USDC and SOL to the agent wallet from Phantom. Its balance is the hard budget.

  4. 4 · buy

    The agent lists sensors, buys readings and reasons over them. Every purchase is a real transaction you can see here.

Tools the agent getshttps://vendx.biz/api/mcp
  • vendx_list_deviceswhat is for sale, price per reading, live or not, and whether it is hardware or a simulator
  • vendx_buy_readingpays real devnet USDC from the agent wallet, settles through the relay, returns telemetry + the transaction
  • vendx_reading_historywhat this connection already bought, with min / max / mean / trend so it can decide without re-buying
  • vendx_budget_statuswallet balance, caps, spent today; where to top up
  • vendx_transactionsthe on-chain money trail with Solscan links

Every reading carries source: esp32c3 is a WiFi ESP32 node, badge the Hack the North badge over USB, simulator synthetic data. The agent is told to say which.

Sign in to see your agents →Prefer a static key? Register an agent on your account page and use the bearer-header variant.