33trust / 100

Cake Servings

by Party & Event Planner in Other

x402 APIFailing, checked 21 h ago

Cake servings from pan size and area per slice: round, square or rectangle, one or several tiers, wedding or party slice style.

GET
https://party-event-calc.x402tookit.com/cake-servings
Price
$0.02
per call in USDC
Uptime
53.9%
last 30 days
Response time
517 ms
875 ms slowest 5%
Last check
Failed
21 h ago, next in 2 h

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 21 h ago: Expected HTTP 402, got 530

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

How to call it

GET https://party-event-calc.x402tookit.com/cake-servings

Each call costs $0.02 in USDC on Polygon, 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://party-event-calc.x402tookit.com/cake-servings?shape=round&sizeIn=6%2C8%2C10&sliceStyle=wedding

Parameters

ParameterTypeRequiredDescription
servingSqInnumberNoYour own area per slice in square inches, replacing the style
shapestringYesround, square or rectangle
sizeInstringYesDiameter or side in inches; for stacked tiers a comma list like 6,8,10 (rectangle: its length, one tier)
sliceStylestringNowedding (2 sq in per slice, a 1 x 2 inch top) or party (4 sq in, 2 x 2 inch). Default wedding
widthInnumberNoWidth in inches (rectangle only)

Example response

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

Example response, 34 lines
{
  "areaPerSliceSqIn": 2,
  "asOf": "2026-10-12T01:45:03.985Z",
  "degraded": false,
  "disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
  "notChecked": [
    "cake height, tier spacing, and how deep a slice is cut",
    "published wedding-cake charts (this uses area per slice, so it can differ by a few servings)",
    "…1 more"
  ],
  "reasons": [
    "Each tier gives whole slices: top area / area per slice, rounded down; the tiers are added.",
    "Round area = pi x radius squared."
  ],
  "shape": "round",
  "sliceStyle": "wedding",
  "source": "computed locally (top area of each tier divided by area per slice; no published serving chart is used)",
  "summary": "78 servings from 3 round tier(s) at 2 sq in a slice (wedding).",
  "tierCount": 3,
  "tiers": [
    {
      "servings": 14,
      "sizeIn": 6,
      "topAreaSqIn": 28.27
    },
    {
      "servings": 25,
      "sizeIn": 8,
      "topAreaSqIn": 50.27
    }
  ],
  "totalServings": 78,
  "verdict": "COMPUTED"
}

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 'https://party-event-calc.x402tookit.com/cake-servings?shape=round&sizeIn=6%2C8%2C10&sliceStyle=wedding'

# 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://party-event-calc.x402tookit.com/cake-servings?shape=round&sizeIn=6%2C8%2C10&sliceStyle=wedding' \
  | 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%2Fparty-event-calc.x402tookit.com%2Fcake-servings
const res = await pay("https://party-event-calc.x402tookit.com/cake-servings?shape=round&sizeIn=6%2C8%2C10&sliceStyle=wedding");
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.get("https://party-event-calc.x402tookit.com/cake-servings?shape=round&sizeIn=6%2C8%2C10&sliceStyle=wedding")
    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
21 h agoExpected HTTP 402, got 530530130 ms-
2 days agoExpected HTTP 402, got 53053095 ms-
3 days agoExpected HTTP 402, got 53053091 ms-
5 days agoExpected HTTP 402, got 530530245 ms-
5 days agoExpected HTTP 402, got 530530188 ms-
Show 8 older checks
5 days agoExpected HTTP 402, got 530530158 ms-
5 days agoPassed402520 ms$0.02
6 days agoPassed402507 ms$0.02
6 days agoPassed402875 ms$0.02
6 days agoPassed402517 ms$0.02
6 days agoPassed402743 ms$0.02
6 days agoPassed402488 ms$0.02
7 days agoPassed402417 ms$0.02