blocknet.

Roadmap

From gateway to enforcement.

Ordered by what unblocks real use first. Targets, not promises.

Done · Nov 2026

Agent Gateway

  • One endpoint for agents, with host allow and deny rules
  • Reads x402 payment requests and picks the cheapest acceptable option
  • Per-request cap, daily budget, review threshold, allowed networks and currencies
  • Trust scores from your settings and Blocknet's own record of each service
  • Single-use, expiring approvals, and a dashboard to approve or deny
  • Append-only audit log; spend survives restarts
  • One command for Claude and other MCP clients, and a drop-in fetch for code
  • Safe with no setup: cloud metadata blocked, an admin token made on first run

Next

Ready for design partners

ItemWhy
Approvals that survive restartsPending payments shouldn't vanish
Per-agent keys and budgetsTeams run many agents; one budget is too coarse
Approval notificationsNobody should have to watch a dashboard
Streaming responsesLarge downloads go through without buffering

Then

Enforcement

ItemWhy
Lockdown recipes for containers and serversMake going through Blocknet the only way out
Wallets that check approvalsEnforce policy where the money moves
Signed approvalsA wallet can verify an approval came from Blocknet
Transparent proxy modeFor agents that can't change how they make requests

Later

Hosted

ItemWhy
Hosted GatewayTeam dashboard and alerts, nothing to run
Blocknet AgentControl which tools and sites agents reach

?

Open questions

  • Do teams need wallet-level enforcement before they'll adopt a gateway?
  • Should budgets belong to each agent, or to the team?
  • How many recorded outcomes before a reputation score can be trusted?
  • Who buys this: platform engineering, security, or finance?

Have an answer? Write to us.

Give your agents a budget, not a blank check.

Blocknet is in development. Write to us if you run agents that call paid services and want to try it early.

contact@acificlabs.com