Eol
by Saylor Innovations Data Desk in Developer tools
End-of-life dates for software - check whether a version of Node.js, Python, Ubuntu, Java, PostgreSQL and 400 other products is still supported, with LTS and latest release
https://saylorinnovations.com/api/eol/:product- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 1 h ago, next any minute now
Reliability
Latest check failed 1 h ago: Expected HTTP 402, got 400
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://saylorinnovations.com/api/eol/:product
Each call costs $0.01 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://saylorinnovations.com/api/eol/:product?version=18Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
version | string | No | optional version to check, e.g. 18 or 3.9 |
Example response
The provider's example. We can't check it without paying.
Example response, 49 lines
{
"cycles": [
{
"cycle": "26",
"days_until_eol": 931,
"eol_date": "2029-04-30",
"is_eol": false,
"latest": "26.11.1",
"lts": "from 2026-10-28",
"release_date": "2026-05-05"
},
{
"cycle": "25",
"days_until_eol": null,
"eol_date": "2026-06-01",
"is_eol": true,
"latest": "25.9.0",
"lts": false,
"release_date": "2025-10-15"
},
{
"cycle": "24",
"days_until_eol": 566,
"eol_date": "2028-04-30",
"is_eol": false,
"latest": "24.21.0",
"lts": true,
"release_date": "2025-05-06"
}
],
"latest_cycle": "26",
"product": "nodejs",
"source": "endoflife.date",
"supported_cycles": [
"26",
"24",
"22"
],
"version": "18",
"version_status": {
"cycle": "18",
"days_until_eol": null,
"eol_date": "2025-04-30",
"is_eol": true,
"latest_in_cycle": "18.20.8",
"lts": true,
"verdict": "end-of-life: upgrade"
}
}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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/eol/:product?version=18'
# 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://saylorinnovations.com/api/eol/:product?version=18' \
| 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Feol%2F%3Aproduct
const res = await pay("https://saylorinnovations.com/api/eol/:product?version=18");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://saylorinnovations.com/api/eol/:product?version=18")
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 |
|---|---|---|---|---|
| 1 h ago | Expected HTTP 402, got 400 | 400 | 464 ms | - |
| 6 h ago | Expected HTTP 402, got 400 | 400 | 869 ms | - |
| 11 h ago | Expected HTTP 402, got 400 | 400 | 213 ms | - |
| 15 h ago | Expected HTTP 402, got 400 | 400 | 197 ms | - |