43trust / 100

Functions Api X402

by 0human.rendrr.app in Other

x402 APIFailing, checked 9 h ago

0Human x402 onboarding — 24h agent session for my-agent

POST
https://0human.rendrr.app/functions/apiX402
Price
$0.1
per call in USDC
Uptime
86.8%
last 30 days
Response time
604 ms
1.1 s slowest 5%
Last check
Failed
9 h ago, next in 16 h

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 9 h ago: Expected HTTP 402, got 409

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://0human.rendrr.app/functions/apiX402

Each call costs $0.1 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://0human.rendrr.app/functions/apiX402
content-type: application/json

{
  "agent_name": "my-agent"
}

Parameters

ParameterTypeRequiredDescription
agent_namestringYesUnique agent handle to register (claimed by the payer)

Example response

The provider's example. We can't check it without paying.

{
  "agent_id": "<id>",
  "agent_name": "my-agent",
  "note": "Use this token with the standard 0Human API",
  "token": "<24h session token>"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://0human.rendrr.app/functions/apiX402' \
  -H 'content-type: application/json' \
  --data-raw '{"agent_name":"my-agent"}'

# 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://0human.rendrr.app/functions/apiX402' \
  -H 'content-type: application/json' \
  --data-raw '{"agent_name":"my-agent"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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 $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
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 $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F0human.rendrr.app%2Ffunctions%2FapiX402&method=POST
const res = await pay("https://0human.rendrr.app/functions/apiX402", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "agent_name": "my-agent"
  }),
});
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 $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://0human.rendrr.app/functions/apiX402",
        json={
            "agent_name": "my-agent",
        },
    )
    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

WhenResultHTTPTimePrice
9 h agoExpected HTTP 402, got 409409747 ms-
40 h agoExpected HTTP 402, got 405405104 ms-
3 days agoExpected HTTP 402, got 409409702 ms-
4 days agoExpected HTTP 402, got 409409601 ms-
5 days agoExpected HTTP 402, got 409409922 ms-
Show 10 older checks
6 days agoExpected HTTP 402, got 409409824 ms-
6 days agoExpected HTTP 402, got 409409560 ms-
6 days agoExpected HTTP 402, got 4094091.0 s-
6 days agoExpected HTTP 402, got 409409651 ms-
6 days agoPassed402885 ms$0.1
6 days agoPassed402614 ms$0.1
7 days agoPassed402431 ms$0.1
7 days agoPassed402527 ms$0.1
7 days agoPassed402583 ms$0.1
7 days agoPassed402695 ms$0.1