Email x402 REST usage
Send email notification for payment confirmations, alerts, receipts.
gateway.spraay.app · 22 listed services · provider site
Send email notification for payment confirmations, alerts, receipts.
List all AI models on Bittensor. OpenAI /v1/models compatible. Drop-in: just change base_url to gateway.spraay.app/bittensor/v1
Web search with clean, LLM-ready results via Tavily. Basic or advanced depth.
List your own scheduled jobs (owned by the paying wallet or API key): status, next run (UTC), runs used and remaining. Optional ?status= and ?action= filters.
Dispatch a paid task to an RTP-registered robot. x402 payment held in escrow until completion.
Chat completions via Bittensor decentralized AI. Fully OpenAI-compatible. 43+ models (DeepSeek, Qwen, Llama, Mistral). Streaming, function calling, TEE-verified. Drop-in: just change base_url.
GPU/Compute — run AI model inference via Replicate (image, video, LLM, audio, utility).
Schedule a recurring trigger: 5-field cron in UTC, at least 1 hour between runs, 100 runs included. On each run the gateway POSTs a signed cron.triggered webhook to your https callback_url; your agent then calls batch/ex...
Estimate batch gas and protocol fee. Units: amounts[] are RAW base units (USDC 6dp: "1500000" = $1.50); totalAmount/fee/totalWithFee are human-decimal strings; suggestedGasLimit is a decimal string.
Cancel one of your own scheduled jobs by jobId so it no longer fires.
Batch payments via Spraay. Implements Batch Payments for Agents (BPA) 1.0 - atomic, non-custodial, up to 200 recipients. Spec: https://docs.spraay.app/bpa/1.0/
AI image generation from text prompts. FLUX Schnell, FLUX Dev, FLUX Pro, Stable Diffusion XL via Replicate. Text to image.
Swap quotes via Uniswap V3.
Pin content to IPFS or Arweave for permanent storage.
Gas prices on Base.
Multi-token price feed.
Stablecoin FX rates.
Send SMS notification for payment alerts.
Payroll stablecoins.
Supported bridge chains.
Query structured logs by service, level, time.
Check KYC verification status.
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.