13trust / 100

Bio Pathways

by Saylor Innovations Bioinformatic in Other

x402 APIFailing, checked 2 min ago

Biological pathways for a gene or protein (Reactome) - pathway ids, names, disease flags and links

GET
https://saylorinnovations.com/api/bio/pathways/:id
Price
$0.002
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
2 min ago, next in 56 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 2 min ago: Expected HTTP 402, got 400

Status and outage history · Atom feed

How to call it

GET https://saylorinnovations.com/api/bio/pathways/:id

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

Built from the input schema. Replace the values with your own.

GET https://saylorinnovations.com/api/bio/pathways/:id?organism=example

Parameters

ParameterTypeRequiredDescription
organismstringNoNCBI taxon id, default 9606 (query)

Example response

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

{
  "accession": "P04637",
  "count": 46,
  "found": true,
  "pathways": [
    {
      "id": "R-HSA-111448",
      "in_disease": false,
      "name": "Activation of NOXA and translocation to mitochondria",
      "url": "https://reactome.org/content/detail/R-HSA-111448"
    }
  ],
  "query": "TP53"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/bio/pathways/:id?organism=example'

# 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/bio/pathways/:id?organism=example' \
  | 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Fbio%2Fpathways%2F%3Aid
const res = await pay("https://saylorinnovations.com/api/bio/pathways/:id?organism=example");
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
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/bio/pathways/:id?organism=example")
    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
2 min agoExpected HTTP 402, got 400400233 ms-
5 h agoExpected HTTP 402, got 400400645 ms-
10 h agoExpected HTTP 402, got 400400276 ms-
14 h agoExpected HTTP 402, got 400400598 ms-
18 h agoExpected HTTP 402, got 400400712 ms-
Show 10 older checks
23 h agoExpected HTTP 402, got 400400207 ms-
27 h agoExpected HTTP 402, got 400400203 ms-
31 h agoExpected HTTP 402, got 400400425 ms-
36 h agoExpected HTTP 402, got 400400928 ms-
40 h agoExpected HTTP 402, got 400400552 ms-
44 h agoExpected HTTP 402, got 400400200 ms-
2 days agoExpected HTTP 402, got 400400352 ms-
2 days agoExpected HTTP 402, got 400400599 ms-
2 days agoExpected HTTP 402, got 400400330 ms-
3 days agoExpected HTTP 402, got 400400246 ms-