ToolVet
77trust / 100

Prime Factorize

by Sindri in Other

x402 APIPassing, checked 2 h ago

Prime factorization of an integer via trial division, returning the full list of prime factors (with repetition).

POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
379 ms typical, 482 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize

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.

POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize
content-type: application/json

{
  "n": 60
}

Parameters

ParameterTypeRequiredDescription
nnumberYesInteger to factorize (2 to 10^12).

Example response

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

{
  "data": {
    "factors": [
      2,
      2,
      3,
      5
    ],
    "params": {
      "n": 60
    }
  },
  "ok": 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 -X POST 'https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize' \
  -H 'content-type: application/json' \
  --data-raw '{"n":60}'

# 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://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize' \
  -H 'content-type: application/json' \
  --data-raw '{"n":60}' \
  | 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%2Fppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws%2FprimeFactorize&method=POST
const res = await pay("https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "n": 60
  }),
});
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.post(
        "https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/primeFactorize",
        json={
            "n": 60,
        },
    )
    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 agoPassed402380 ms$0.01
6 h agoPassed402120 ms$0.01
10 h agoPassed402116 ms$0.01
13 h agoPassed402500 ms$0.01
17 h agoPassed402482 ms$0.01
21 h agoPassed402421 ms$0.01
25 h agoPassed402349 ms$0.01
28 h agoPassed402339 ms$0.01
32 h agoPassed402389 ms$0.01
35 h agoPassed402129 ms$0.01
39 h agoPassed402441 ms$0.01
43 h agoPassed402131 ms$0.01
46 h agoPassed402376 ms$0.01
2 days agoPassed402121 ms$0.01
2 days agoPassed402461 ms$0.01