Sym Where
by s2ar in Search & web
Code search by meaning in a GitHub repo — the definitions matching a question, with file and lines. GET ?repo=&query=
https://api.s2ar.dev/x402/v1/sym/where- Price
- $0.01
- per call in USDC
- Uptime
- 73.0%
- last 30 days
- Response time
- 370 ms
- 452 ms slowest 5%
- Last check
- Failed
- 4 h ago, next any minute now
Reliability
Latest check failed 4 h ago: Expected HTTP 402, got 410
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.s2ar.dev/x402/v1/sym/where
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://api.s2ar.dev/x402/v1/sym/where?query=how+are+glob+overrides+applied&ref=14.1.1&repo=BurntSushi%2FripgrepParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
k | string | No | hits to return (default 8) |
query | string | Yes | |
ref | string | No | branch, tag or commit; the default branch when omitted |
repo | string | Yes | a public GitHub, GitLab or Codeberg repository: owner/repo, github.com/owner/repo or its https URL |
Example response
The provider's example. We can't check it without paying.
{
"charged_usd": 0.01,
"ok": true,
"receipt": {
"charter": "https://api.s2ar.dev/charter",
"cost_usd": 0.01,
"determinism": "replayable",
"evidence_hash": "sha256:94abfed2…",
"issued_at": "2026-10-10T00:00:00Z",
"refund_rule": "failed calls are never charged",
"what": "…",
"witnesses": [
"sym"
]
},
"ref": "14.1.1",
"repo": "https://github.com/BurntSushi/ripgrep",
"text": "crates/ignore/src/overrides.rs:…",
"tokens_est": 400
}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://api.s2ar.dev/x402/v1/sym/where?query=how+are+glob+overrides+applied&ref=14.1.1&repo=BurntSushi%2Fripgrep'
# 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.s2ar.dev/x402/v1/sym/where?query=how+are+glob+overrides+applied&ref=14.1.1&repo=BurntSushi%2Fripgrep' \
| 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%2Fapi.s2ar.dev%2Fx402%2Fv1%2Fsym%2Fwhere
const res = await pay("https://api.s2ar.dev/x402/v1/sym/where?query=how+are+glob+overrides+applied&ref=14.1.1&repo=BurntSushi%2Fripgrep");
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://api.s2ar.dev/x402/v1/sym/where?query=how+are+glob+overrides+applied&ref=14.1.1&repo=BurntSushi%2Fripgrep")
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 |
|---|---|---|---|---|
| 4 h ago | Expected HTTP 402, got 410 | 410 | 336 ms | - |
| 9 h ago | Expected HTTP 402, got 410 | 410 | 377 ms | - |
| 15 h ago | Expected HTTP 402, got 410 | 410 | 427 ms | - |
| 20 h ago | Expected HTTP 402, got 410 | 410 | 429 ms | - |
| 26 h ago | Expected HTTP 402, got 410 | 410 | 352 ms | - |
Show 10 older checks
| 31 h ago | Expected HTTP 402, got 410 | 410 | 377 ms | - |
| 36 h ago | Expected HTTP 402, got 410 | 410 | 342 ms | - |
| 41 h ago | Expected HTTP 402, got 410 | 410 | 449 ms | - |
| 46 h ago | Expected HTTP 402, got 410 | 410 | 301 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 369 ms | - |
| 2 days ago | Passed | 402 | 381 ms | $0.01 |
| 2 days ago | Passed | 402 | 432 ms | $0.01 |
| 3 days ago | Passed | 402 | 379 ms | $0.01 |
| 3 days ago | Passed | 402 | 339 ms | $0.01 |
| 3 days ago | Passed | 402 | 350 ms | $0.01 |