https://api.agentstools.devKeyword news search across web news engines (Bing/DuckDuckGo/Yahoo via ddgs). Returns dated headlines with title/url/snippet/source/image + freshness/region/safesearch filters.
Free-text web search for AI agents: ranked title/url/snippet results fused across multiple engines (Brave, Google, DuckDuckGo, Mojeek, Startpage, Yahoo), with freshness filters (past day/week/month/year), region/locale and SafeSearch. One call for grounded, up-to-date web results — no keys, no scraping setup.
Fetch any public web page and return its main readable content as clean Markdown or plain text plus metadata (title), stripping nav/ads/boilerplate (trafilatura). Optional JS rendering via headless browser for SPAs; markdown or text output. Robots-respecting, public content only — the reader/scraper building block for RAG and agent pipelines.
Compute keccak256/sha256, a 4-byte function selector, an event topic0, or an ENS namehash/labelhash from a string or hex input.
Crypto Fear & Greed Index: the market Fear & Greed value, classification and trend, blended with aggregated crypto news-headline sentiment into one bullish/bearish/neutral score, optionally focused on a coin or query. Data by alternative.me (attributed) + curated RSS headlines.
Check whether a crypto address appears on the official public sanctions lists (OFAC SDN, UK, EU, UN). Deterministic exact lookup; returns the matched record (list, program, entity name, reference, currency).
Reputation of a public IP address for anti-abuse and KYC. Returns ASN, AS-org, country, datacenter/hosting classification, Tor-exit and Spamhaus DROP flags, plus a deterministic risk score with reasons.
On-chain USD spot price for 50+ assets from Chainlink feeds or the most-liquid Base DEX pool (computed from public chain state): crypto majors, stablecoins, Base-native tokens, forex currencies and precious metals.
Detail of ONE prediction market or event by numeric id, 0x conditionId, market-slug or event-slug (auto-detected): normalized outcomes with implied probabilities, volume, liquidity, close date, status and a link-back.
Fusion flow brief for spot Bitcoin or Ethereum ETFs in ONE call: latest total net flow, the inflow/outflow streak, the window cumulative, flow momentum, issuer concentration, total AUM and a deterministic accumulation, distribution or neutral verdict. Saves several issuer queries plus the differencing.
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the native x402 API at: https://api.agentstools.dev ** Payment method ** This endpoint is hosted outside FluxA and is called directly, not through the FluxA proxy. It settles on-chain in USDC via x402. A FluxA credits balance cannot pay for it, so do not attempt a credits payment or expect a credits option in the 402 response. Follow the steps below in order. ** Step 1 - Install FluxA Wallet CLI ** npm install -g @fluxa-pay/fluxa-wallet Or use without installing: npx fluxa-wallet <command> ** Step 2 - Register agent ** fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>" The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser. Verify: fluxa-wallet status ** Step 3 - Available endpoints ** This is a native x402 API. The known endpoints are: ** Step 4 - Create an intent mandate ** x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits. Payment is in on-chain USDC. Amounts are in atomic units (6 decimals, e.g., 100000 = 0.10 USDC). fluxa-wallet mandate-create \ --desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \ --amount <BUDGET_IN_ATOMIC_UNITS> \ --seconds <DURATION_IN_SECONDS> Options: - --desc (required): Human-readable spending plan description - --amount (required): Budget in USDC atomic units (6 decimals) - --seconds (optional, default 28800 = 8h): Duration in seconds ** Step 5 - Get user to sign the mandate ** The response from Step 4 includes mandateId and authorizationUrl (TTL: 10 minutes). Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser. ** Step 6 - Wait for mandate to be signed ** fluxa-wallet mandate-status --id <MANDATE_ID> Poll until mandate.status is "signed". The response also includes remainingAmount. Important: Use --id, not --mandate. ** Step 7 - Call the API ** Make the API request to the endpoint URL. If it returns HTTP 402, continue to Step 8. ** Step 8 - Pay via x402 v3 ** Pass the complete HTTP 402 response body as --payload: fluxa-wallet x402-v3 \ --mandate <MANDATE_ID> \ --payload '$PAYLOAD_402' The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON. The response includes xPaymentB64 (the payment token). ** Step 9 - Retry with payment token ** curl -H "Payment-Signature: <xPaymentB64>" <ORIGINAL_API_URL> Return the raw API response to the user without post-processing. ** Opening links for user ** Whenever you need to open a URL (authorization, approval, or any external link): 1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool) 2. Options: [Yes, open the link] [No, don't open] 3. If YES: run 'open "<URL>"' to open in their default browser 4. If NO: ask how they would like to proceed ** Error handling ** - mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl - mandate_expired: Time window passed - create a new mandate - mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit - agent_not_registered: No Agent ID - run 'fluxa-wallet init' first - Invalid payload: missing accepts array: Pass the full 402 response JSON