Sec Financials
by TickersFeed in Markets & finance
Company financial statements parsed from SEC XBRL data — revenue, net income, EPS, assets, liabilities, and equity across recent periods as structured JSON. Use for: fundamental analysis, income statement and balance sheet data, financial ratio calculation, valuation, earnings quality research. $0.008 USDC per call.
https://api.tickersfeed.net/sec/:symbol/financials- Price
- $0.008
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Expected HTTP 402, got 404
How to call it
GET https://api.tickersfeed.net/sec/:symbol/financials
Each call costs $0.008 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/sec/:symbol/financials?limit=10&symbol=AAPLParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | No | Number of periods (default 4) |
symbol | string | No | Stock ticker symbol (e.g. AAPL, MSFT) |
Example response
The provider's example. We can't check it without paying.
{
"financials": {
"revenue": [
{
"form": "10-K",
"period": "2024-09-30",
"value": 394328000000
}
]
},
"symbol": "AAPL"
}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.008.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.tickersfeed.net/sec/:symbol/financials?limit=10&symbol=AAPL'
# 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/sec/:symbol/financials?limit=10&symbol=AAPL' \
| 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.008 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.008" });
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.008 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.tickersfeed.net%2Fsec%2F%3Asymbol%2Ffinancials
const res = await pay("https://api.tickersfeed.net/sec/:symbol/financials?limit=10&symbol=AAPL");
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.008 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.008"})
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/sec/:symbol/financials?limit=10&symbol=AAPL")
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 |
|---|---|---|---|---|
| 3 h ago | Expected HTTP 402, got 404 | 404 | 448 ms | - |
| 8 h ago | Expected HTTP 402, got 404 | 404 | 353 ms | - |
| 12 h ago | Expected HTTP 402, got 404 | 404 | 425 ms | - |
| 17 h ago | Expected HTTP 402, got 404 | 404 | 460 ms | - |
| 21 h ago | Expected HTTP 402, got 404 | 404 | 414 ms | - |
Show 10 older checks
| 26 h ago | Expected HTTP 402, got 404 | 404 | 125 ms | - |
| 30 h ago | Expected HTTP 402, got 404 | 404 | 127 ms | - |
| 35 h ago | Expected HTTP 402, got 404 | 404 | 402 ms | - |
| 39 h ago | Expected HTTP 402, got 404 | 404 | 512 ms | - |
| 43 h ago | Expected HTTP 402, got 404 | 404 | 122 ms | - |
| 47 h ago | Expected HTTP 402, got 404 | 404 | 471 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 440 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 324 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 515 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 453 ms | - |