Projects Activate
by x402 Hosting in Developer tools
Activate a newly created project so its site goes live, paying per day of hosting (1-730 days via the days query parameter). Call this after the first deployment is queued; only the owner wallet bound at creation can pay.
POST https://api.x402-hosting.com/v1/projects/:id/activate
Last 30 days
- Uptime
- 0.0%
- Response time
- - typical, - slowest 5%
- Last check
- 4 h ago: Expected HTTP 402, got 500
- Next check
- any minute now
How to call it
POST https://api.x402-hosting.com/v1/projects/:id/activate
Each call costs $6.00 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.x402-hosting.com/v1/projects/:id/activate
content-type: application/json
{
"days": 1
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | Yes |
Example response
The provider's example. We can't check it without paying.
{
"operationId": "00000000-0000-4000-8000-000000000001",
"operationUrl": "/v1/operations/00000000-0000-4000-8000-000000000001",
"projectId": "00000000-0000-4000-8000-000000000001",
"state": "CREATED"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $6.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.x402-hosting.com/v1/projects/:id/activate' \
-H 'content-type: application/json' \
--data-raw '{"days":1}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.x402-hosting.com/v1/projects/:id/activate' \
-H 'content-type: application/json' \
--data-raw '{"days":1}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $6 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$6" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $6 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.x402-hosting.com%2Fv1%2Fprojects%2F%3Aid%2Factivate&method=POST
const res = await pay("https://api.x402-hosting.com/v1/projects/:id/activate", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"days": 1
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $6 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$6"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.x402-hosting.com/v1/projects/:id/activate",
json={
"days": 1,
},
)
print(res.status_code, res.text)Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Expected HTTP 402, got 500 | 500 | 423 ms | - |
| 8 h ago | Expected HTTP 402, got 500 | 500 | 290 ms | - |
| 13 h ago | Expected HTTP 402, got 500 | 500 | 497 ms | - |
| 17 h ago | Expected HTTP 402, got 500 | 500 | 481 ms | - |
| 21 h ago | Expected HTTP 402, got 500 | 500 | 431 ms | - |
| 25 h ago | Expected HTTP 402, got 500 | 500 | 380 ms | - |
| 29 h ago | Expected HTTP 402, got 500 | 500 | 341 ms | - |
| 33 h ago | Expected HTTP 402, got 500 | 500 | 405 ms | - |
| 37 h ago | Expected HTTP 402, got 500 | 500 | 402 ms | - |
| 41 h ago | Expected HTTP 402, got 500 | 500 | 495 ms | - |
| 46 h ago | Expected HTTP 402, got 500 | 500 | 448 ms | - |
| 2 days ago | Expected HTTP 402, got 500 | 500 | 548 ms | - |
| 2 days ago | Expected HTTP 402, got 500 | 500 | 374 ms | - |
| 2 days ago | Expected HTTP 402, got 500 | 500 | 517 ms | - |
| 3 days ago | Expected HTTP 402, got 500 | 500 | 393 ms | - |