13trust / 100

Corner Cards

by FootballPulse in Markets & finance

x402 APIFailing, checked 4 h ago

Corner and booking markets — corner stats, booking points, referee card rates and over/under probabilities. For football specialty-market betting agents.

GET
https://footballpulse.theaslangroupllc.com/api/corner-cards
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

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

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://footballpulse.theaslangroupllc.com/api/corner-cards

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://footballpulse.theaslangroupllc.com/api/corner-cards?away=away+team+name&competition=competition+name+for+context&home=home+team+name&lang=en&referee=referee+name+for+booking+points+analysis

Parameters

ParameterTypeRequiredDescription
awaystringNorequired
competitionstringNooptional
homestringNorequired
langstringNoen | es | fr | de | pt | ja | zh | ko | ar (default: en)
refereestringNooptional

Example response

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

{
  "bookings": {
    "booking_points_expected": 32,
    "bookings_verdict": "Expect a card-heavy affair — referee averages 4.2 cards per game",
    "over_30_points_probability": "54%"
  },
  "corners": {
    "away_avg_for": 5.2,
    "combined_expected": 10.8,
    "corner_verdict": "Back over 9.5 corners — both teams average high corner counts",
    "home_avg_for": 6.8,
    "over_9_5_probability": "62%"
  },
  "match": {
    "away": "Chelsea",
    "competition": "Premier League",
    "home": "Arsenal"
  }
}

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://footballpulse.theaslangroupllc.com/api/corner-cards?away=away+team+name&competition=competition+name+for+context&home=home+team+name&lang=en&referee=referee+name+for+booking+points+analysis'

# 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://footballpulse.theaslangroupllc.com/api/corner-cards?away=away+team+name&competition=competition+name+for+context&home=home+team+name&lang=en&referee=referee+name+for+booking+points+analysis' \
  | 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.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%2Ffootballpulse.theaslangroupllc.com%2Fapi%2Fcorner-cards
const res = await pay("https://footballpulse.theaslangroupllc.com/api/corner-cards?away=away+team+name&competition=competition+name+for+context&home=home+team+name&lang=en&referee=referee+name+for+booking+points+analysis");
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://footballpulse.theaslangroupllc.com/api/corner-cards?away=away+team+name&competition=competition+name+for+context&home=home+team+name&lang=en&referee=referee+name+for+booking+points+analysis")
    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 agoAmount "0.1" is not in atomic token units402331 ms$0.1
10 h agoAmount "0.1" is not in atomic token units402253 ms$0.1
16 h agoAmount "0.1" is not in atomic token units402251 ms$0.1
22 h agoAmount "0.1" is not in atomic token units402218 ms$0.1
27 h agoAmount "0.1" is not in atomic token units402254 ms$0.1
Show 7 older checks
33 h agoAmount "0.1" is not in atomic token units402220 ms$0.1
38 h agoAmount "0.1" is not in atomic token units402196 ms$0.1
44 h agoAmount "0.1" is not in atomic token units402199 ms$0.1
2 days agoAmount "0.1" is not in atomic token units402194 ms$0.1
2 days agoAmount "0.1" is not in atomic token units402208 ms$0.1
2 days agoAmount "0.1" is not in atomic token units402445 ms$0.1
3 days agoAmount "0.1" is not in atomic token units402460 ms$0.1