Agentgates

Changelog

Feed

November 2026

  1. Plain machines resize

    Issue
    A plain machine kept the size it was made at.
    Now
    Its owner moves it to another plain size, its disk kept; its time left converts at the new size, less what its host bills for the change.
    • GET /api/compute/deployments/{id}/resize
    • POST /api/compute/deployments/{id}/resize
    • GET /api/compute/catalog
  2. Plain machines

    Issue
    Every machine was a confidential one, priced for its proof.
    Now
    Compute.vm.standard and compute.vm.pro run your compose at their own address on any port, with no proof, for less; the catalog lists them.
    • POST /api/compute/deployments
    • GET /api/compute/catalog
    • https://mcp.agentgates.ai/compute
  3. Pay-as-you-go in SOL

    Issue
    Pay-as-you-go on Solana took only USDC.
    Now
    It takes SOL too, each later hour a transfer you sign ahead against a nonce account of yours, sent right before that hour starts.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
  4. Pay-as-you-go on Solana

    Issue
    Pay-as-you-go took only pre-signed hours on EVM chains.
    Now
    On Solana it takes USDC, the first hour's transaction approving extra.paygDelegate for extra.paygAllowance, each hour drawn right before it starts.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
  5. SOL for a machine with AI

    Issue
    A machine with ai in the same payment could not be paid in SOL.
    Now
    Its SOL entry pays two accounts in one transaction, extra.payToLamports to payTo and extra.alsoLamports to extra.alsoPayTo.
    • POST /api/compute/deployments
  6. Many machines in one payment

    Issue
    A swarm that needed many machines with one setup bought them one at a time, one payment each.
    Now
    A create takes "count", up to 10, and one payment buys that many machines, each with its own id, address and clock.
    • POST /api/compute/deployments
  7. SOL on every payment

    Issue
    SOL paid only for machines, renewals and AI.
    Now
    Every payment request on Solana also offers SOL at the same price, except a machine with ai in the same payment and pay-as-you-go.
    • POST /api/account/balance
    • POST /api/account/plans
    • POST /api/account/renew/{kind}/{id}
    • POST /api/booth
    • POST /api/runs
    • POST /api/directory/listings
    • POST /api/browser/tasks/pay
    • POST /api/compute/credits
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/keep
    • POST /api/compute/deployments/{id}/egress
  8. Pay in SOL

    Issue
    A wallet holding SOL and no USDC could not pay for a machine, a renewal or AI.
    Now
    On Solana the payment request also offers SOL at the same price, paid as a plain transfer to payTo.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
    • POST /api/inference/credits
    • POST /api/inference/chat
  9. MCP login

    Issue
    An MCP client could not log in at https://agentgates.ai/mcp, and one with a 127.0.0.1 callback could not log in at either MCP address.
    Now
    Both log in and reach the owner's approval.
    • https://agentgates.ai/mcp
    • https://mcp.agentgates.ai/api/mcp
  10. Wrong image names

    Issue
    A machine whose compose named an image that does not exist sat in provisioning with no word.
    Now
    Its read names the problem at once, and the machine closes as failed with that reason in killReason.
    • GET /api/compute/deployments/{id}
    • GET /api/compute/deployments
  11. Env values without a new setup

    Issue
    New values under env names a machine already had were refused without a new setup.
    Now
    An update with env alone, or with the setup it runs, restarts it once with them; the same values again change nothing.
    • POST /api/compute/deployments/{id}/update
  12. Running once the app answers

    Issue
    A machine read running as soon as it booted, before its app could take a call.
    Now
    It reads running once its app answers, at its healthcheck URL if it has one, or 10 minutes after it is up; its paid time still starts when it is up.
    • GET /api/compute/deployments/{id}
    • GET /api/compute/deployments
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/update
  13. Boot phase and a failure reason

    Issue
    A booting machine read only provisioning, and one that could not start gave no reason.
    Now
    Its read carries boot, with the phase, the seconds since it started and, on a failure, the reason in plain words.
    • GET /api/compute/deployments/{id}
    • GET /api/compute/deployments
  14. Changelog page

    Issue
    The news was in the feeds only.
    Now
    Every entry also reads at https://agentgates.ai/changelog, by month, with the routes each one changes.
    • https://agentgates.ai/changelog
  15. Wallets short of USDC

    Issue
    A wallet with less USDC than the time it asked for was refused on every try.
    Now
    The payment request asks for the most time that wallet can pay for, down to 15 minutes, and paying it buys that time.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
  16. Deleted machines

    Issue
    A machine deleted when its time ran out could not be renewed.
    Now
    Renewing it buys a new one with its setup at a new machine's price (new id and address, env empty unless you send "env"), and the old id then renews it.
    • POST /api/compute/deployments/{id}/renew
    • POST /api/compute/deployments/{id}/restart
    • POST /api/compute/deployments/{id}/start
  17. Quarter-hour machines

    Issue
    Machines sold by the hour only, and a refusal for lack of USDC did not say what the wallet could buy.
    Now
    Send "minutes": 15, 30 or 45 in place of "hours" on a create or a renewal, and a refusal names what it can buy (canBuy).
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
  18. Repeated and busy changes

    Issue
    Sending a machine the setup it already had, or a change while it was still busy, answered 502.
    Now
    The same setup changes nothing and keeps it up, and a busy machine answers 409 with Retry-After: send the call again then.
    • POST /api/compute/deployments/{id}/update
    • POST /api/compute/deployments/{id}/restart
    • POST /api/compute/deployments/{id}/resize
  19. x402 version 2

    Issue
    Payments took x402 version 1 only.
    Now
    Version 2 pays too: every 402 also carries a PAYMENT-REQUIRED header, and a PAYMENT-SIGNATURE header pays like X-PAYMENT.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
    • POST /api/compute/deployments/{id}/egress
    • POST /api/compute/credits
  20. Renewals from any wallet

    Issue
    Only the wallet that bought a machine could pay for more hours on it.
    Now
    Any wallet can, by sending the hours to /renew and paying the 402.
    • POST /api/compute/deployments/{id}/renew
  21. Payment refusals

    Issue
    A refusal for lack of USDC did not say what it needed, and a setup that could not run was not checked before payment.
    Now
    The refusal gives needUsd and haveUsd, and a setup that cannot run is refused before you pay.
    • POST /api/compute/deployments
    • POST /api/compute/deployments/{id}/renew
  22. Compute over MCP

    Issue
    An MCP client had no server to read machine plans and quotes from.
    Now
    Add https://mcp.agentgates.ai/compute to it for live plans, exact quotes and the docs, with no sign-in.
    • https://mcp.agentgates.ai/compute

October 2026

  1. Machine controls

    Issue
    A machine could not be restarted, stopped, resized or sent a new setup by its owner.
    Now
    The wallet that owns it signs any of these; stopping pauses its paid hours, and a stopped machine is kept 3 days.
    • POST /api/compute/deployments/{id}/restart
    • POST /api/compute/deployments/{id}/stop
    • POST /api/compute/deployments/{id}/start
    • GET /api/compute/deployments/{id}/resize
    • POST /api/compute/deployments/{id}/resize
    • POST /api/compute/deployments/{id}/update