Fit Race
by FitPulse in Other
Race training plan / marathon & 5K prep by race date: build a plan backwards from event day. Returns periodization, weekly mileage, taper, and race-day strategy tuned to race type, date, current fitness, and runs per week. Fitness-info for athlete and coaching agents.
https://fitpulse.theaslangroupllc.com/api/fit/race- Price
- $0.1
- 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
Reliability
Latest check failed 4 h ago: Amount "0.1" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://fitpulse.theaslangroupllc.com/api/fit/race
Each call costs $0.1 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://fitpulse.theaslangroupllc.com/api/fit/raceParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
current_fitness | string | No | Current fitness level and recent training context |
lang | string | No | Response language |
race_date | string | Yes | Race date (YYYY-MM-DD) — plan is built backwards from this date |
race_type | string | Yes | Race type (5K, 10K, half-marathon, marathon, triathlon-sprint, triathlon-olympic, ironman, OCR) |
runs_per_week | string | No | Available training days per week |
Example response
The provider's example. We can't check it without paying.
{
"race_type": "half-marathon",
"taper_plan": "2-week taper, reduce volume 40-60%",
"weeks_to_race": 12
}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 'https://fitpulse.theaslangroupllc.com/api/fit/race'
# 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://fitpulse.theaslangroupllc.com/api/fit/race' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Ffitpulse.theaslangroupllc.com%2Fapi%2Ffit%2Frace
const res = await pay("https://fitpulse.theaslangroupllc.com/api/fit/race");
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.get("https://fitpulse.theaslangroupllc.com/api/fit/race")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Amount "0.1" is not in atomic token units | 402 | 249 ms | $0.1 |
| 12 h ago | Amount "0.1" is not in atomic token units | 402 | 270 ms | $0.1 |
| 21 h ago | Amount "0.1" is not in atomic token units | 402 | 259 ms | $0.1 |
| 29 h ago | Amount "0.1" is not in atomic token units | 402 | 276 ms | $0.1 |
| 37 h ago | Amount "0.1" is not in atomic token units | 402 | 270 ms | $0.1 |
Show 10 older checks
| 45 h ago | Amount "0.1" is not in atomic token units | 402 | 248 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 238 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 238 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 265 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 240 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 304 ms | $0.1 |
| 4 days ago | Amount "0.1" is not in atomic token units | 402 | 280 ms | $0.1 |
| 4 days ago | Amount "0.1" is not in atomic token units | 402 | 266 ms | $0.1 |
| 4 days ago | Amount "0.1" is not in atomic token units | 402 | 198 ms | $0.1 |
| 5 days ago | Amount "0.1" is not in atomic token units | 402 | 203 ms | $0.1 |