13trust / 100

Links

by 50% to Aura Rewards in Other

x402 APIFailing, checked 4 h ago

test payment link that sends 50% to aura rewards multisig

GET
https://api.21.cash/api/links/:address
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 4 h ago: Expected HTTP 402, got 404

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

How to call it

GET https://api.21.cash/api/links/:address

Each call costs $0.01 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.

GET https://api.21.cash/api/links/:address

Example response

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

{
  "content": {
    "description": "test payment link that sends 50% to aura rewards multisig",
    "name": "50% to Aura Rewards",
    "routerAddress": "0x8c913b70Db8FAcDAdc37BC2530559DBE879b95b5"
  },
  "message": "Payment successful! Thank you for your business.",
  "receipt": {
    "network": "eip155:8453",
    "transactionHash": "0x…"
  },
  "success": true
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.21.cash/api/links/:address'

# 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 - 'https://api.21.cash/api/links/:address' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.21.cash%2Fapi%2Flinks%2F%3Aaddress
const res = await pay("https://api.21.cash/api/links/:address");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.21.cash/api/links/:address")
    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
4 h agoExpected HTTP 402, got 404404203 ms-
12 h agoExpected HTTP 402, got 404404230 ms-
21 h agoExpected HTTP 402, got 404404202 ms-
29 h agoExpected HTTP 402, got 404404333 ms-
37 h agoExpected HTTP 402, got 404404209 ms-
Show 10 older checks
45 h agoExpected HTTP 402, got 404404205 ms-
2 days agoExpected HTTP 402, got 404404189 ms-
3 days agoExpected HTTP 402, got 404404219 ms-
3 days agoExpected HTTP 402, got 404404203 ms-
3 days agoExpected HTTP 402, got 404404201 ms-
3 days agoExpected HTTP 402, got 404404170 ms-
4 days agoExpected HTTP 402, got 404404207 ms-
4 days agoExpected HTTP 402, got 404404200 ms-
4 days agoExpected HTTP 402, got 404404259 ms-
5 days agoExpected HTTP 402, got 404404172 ms-