ToolVet
81trust / 100

Twitter Search

by x402.orthogonal.com in Search & web

x402 APIPassing, checked 2 h ago

Search tweets by query string. Supports Twitter search operators. Pagination billing: call the first page normally and save billing.requestId from the Orthogonal /v1/run response. For later page, offset, or cursor calls on the same logical search, pass parentRequestId with unchanged non-pagination parameters. Valid continuation calls still get their own request IDs and quoted price, but are charged 0. Changing filters starts a new billable request.

POST https://x402.orthogonal.com/fiber/v1/twitter/search

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
275 ms typical, 419 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://x402.orthogonal.com/fiber/v1/twitter/search

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

POST https://x402.orthogonal.com/fiber/v1/twitter/search
content-type: application/json

{
  "query": "query"
}

Parameters

ParameterTypeRequiredDescription
cursorstringNoPagination cursor. For later cursor pages of the same logical search, keep non-pagination parameters unchanged and pass top-level parentRequestId from the first Orthogonal /v1/run response.
querystringNoTweet search query.

Example response

The listing has no example response.

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://x402.orthogonal.com/fiber/v1/twitter/search' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"query"}'

# 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 - -X POST 'https://x402.orthogonal.com/fiber/v1/twitter/search' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"query"}' \
  | 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.04 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.04" });
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.04 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402.orthogonal.com%2Ffiber%2Fv1%2Ftwitter%2Fsearch&method=POST
const res = await pay("https://x402.orthogonal.com/fiber/v1/twitter/search", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "query": "query"
  }),
});
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.04 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.04"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://x402.orthogonal.com/fiber/v1/twitter/search",
        json={
            "query": "query",
        },
    )
    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 h agoPassed402182 ms$0.04
7 h agoPassed402447 ms$0.04
11 h agoPassed402417 ms$0.04
14 h agoPassed402303 ms$0.04
18 h agoPassed402185 ms$0.04
22 h agoPassed402272 ms$0.04
26 h agoPassed402192 ms$0.04
30 h agoPassed402339 ms$0.04
33 h agoPassed402251 ms$0.04
37 h agoPassed402243 ms$0.04
40 h agoPassed402275 ms$0.04
44 h agoPassed402419 ms$0.04
47 h agoPassed402303 ms$0.04
2 days agoPassed402228 ms$0.04
2 days agoPassed402398 ms$0.04