71trust / 100

Starship Callsigns

by Starship callsigns in Markets & finance

x402 APIPassing, checked 2 h ago

Starship callsigns: Short ship names suitable for manifests, radios, and game UI.

POST https://market.datapackvibe.com/x402/starship-callsigns

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
68.4%
Response time
70 ms typical, 729 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://market.datapackvibe.com/x402/starship-callsigns

Each call costs $0.02 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://market.datapackvibe.com/x402/starship-callsigns
content-type: application/json

{
  "count": 5
}

Parameters

ParameterTypeRequiredDescription
countintegerNo Default: 5.
seedstringNoOptional repeatable seed.
themestringNoOptional world or project theme.

Example response

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

{
  "files": [],
  "order_id": "ord_example",
  "result": {
    "names": [
      "Vey Reach",
      "Kora Haven"
    ],
    "seed": "abc123"
  },
  "sku": "starship-callsigns",
  "status": "delivered"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://market.datapackvibe.com/x402/starship-callsigns' \
  -H 'content-type: application/json' \
  --data-raw '{"count":5}'

# 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://market.datapackvibe.com/x402/starship-callsigns' \
  -H 'content-type: application/json' \
  --data-raw '{"count":5}' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fmarket.datapackvibe.com%2Fx402%2Fstarship-callsigns&method=POST
const res = await pay("https://market.datapackvibe.com/x402/starship-callsigns", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "count": 5
  }),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://market.datapackvibe.com/x402/starship-callsigns",
        json={
            "count": 5,
        },
    )
    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
2 h agoPassed40268 ms$0.02
5 h agoExpected HTTP 402, got 53053036 ms-
9 h agoExpected HTTP 402, got 53053034 ms-
13 h agoPassed40253 ms$0.02
17 h agoPassed40270 ms$0.02
21 h agoPassed40262 ms$0.02
24 h agoPassed40270 ms$0.02
28 h agoExpected HTTP 402, got 53053041 ms-
31 h agoExpected HTTP 402, got 53053035 ms-
35 h agoExpected HTTP 402, got 53053038 ms-
38 h agoPassed40265 ms$0.02
42 h agoPassed40263 ms$0.02
45 h agoPassed40265 ms$0.02
2 days agoPassed4022.3 s$0.02
2 days agoPassed402172 ms$0.02