79trust / 100

Calendar Earnings

by TickersFeed in Markets & finance

x402 APIPassing, checked 44 min ago

Upcoming US company earnings calendar — which companies report in a date window, with estimated EPS and revenue, as JSON. Default is the next 7 days; filter with ?from=YYYY-MM-DD&to=YYYY-MM-DD (window up to 30 days) or ?symbol=AAPL. Use for: earnings season monitoring, upcoming earnings this week, portfolio earnings alerts, event-driven trading calendar, pre-earnings positioning. $0.005 USDC per call.

GET
https://api.tickersfeed.net/calendar/earnings
Price
$0.005
per call in USDC
Uptime
100%
last 30 days
Response time
438 ms
498 ms slowest 5%
Last check
Passed
44 min ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

GET https://api.tickersfeed.net/calendar/earnings

Each call costs $0.005 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.

GET https://api.tickersfeed.net/calendar/earnings?from=2026-07-29&symbol=AAPL&to=2026-08-05

Parameters

ParameterTypeRequiredDescription
fromstringNoStart date YYYY-MM-DD (default today)
symbolstringNoOptional ticker filter (e.g. AAPL)
tostringNoEnd date YYYY-MM-DD (default +7 days, window ≤30d)

Example response

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

{
  "count": 2,
  "earnings": [
    {
      "date": "2026-07-31",
      "eps_estimate": 1.6,
      "hour": "amc",
      "quarter": 3,
      "revenue_estimate": 94000000000,
      "symbol": "AAPL",
      "year": 2026
    }
  ],
  "from": "2026-07-29",
  "to": "2026-08-05"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.tickersfeed.net/calendar/earnings?from=2026-07-29&symbol=AAPL&to=2026-08-05'

# 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://api.tickersfeed.net/calendar/earnings?from=2026-07-29&symbol=AAPL&to=2026-08-05' \
  | 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.tickersfeed.net%2Fcalendar%2Fearnings
const res = await pay("https://api.tickersfeed.net/calendar/earnings?from=2026-07-29&symbol=AAPL&to=2026-08-05");
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.tickersfeed.net/calendar/earnings?from=2026-07-29&symbol=AAPL&to=2026-08-05")
    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
44 min agoPassed402454 ms$0.005
5 h agoPassed402400 ms$0.005
9 h agoPassed402468 ms$0.005
13 h agoPassed402413 ms$0.005
17 h agoPassed402456 ms$0.005
Show 10 older checks
21 h agoPassed402506 ms$0.005
25 h agoPassed402494 ms$0.005
29 h agoPassed402498 ms$0.005
33 h agoPassed402438 ms$0.005
36 h agoPassed402476 ms$0.005
40 h agoPassed402395 ms$0.005
44 h agoPassed402433 ms$0.005
47 h agoPassed402463 ms$0.005
2 days agoPassed402412 ms$0.005
2 days agoPassed402388 ms$0.005