All services

A great map with info on Capitals all around the world

An MCP server that provides email capabilities, hosted on Alpic platform

Pay-per-call UK intelligence for AI agents, as clean JSON. Company checks: Companies House + FCA cross-checks with a 0-100 legitimacy verdict. Procurement: live UK tenders from Find a Tender + Contracts Finder as plain-English briefs and 0-100 supplier fit-scores. Grants: live GOV.UK funding calls matched to a project profile with ELIGIBLE/UNCERTAIN/INELIGIBLE verdicts, plus funder giving-history from the 360Giving open-data corpus. No signup, no API key.

Tenant-scoped control plane over the ClutchCall platform's full API surface

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key

Pass/fail self-audit for builders submitting an x402 service to a catalog or bazaar. Checks the failure modes that get services rejected or marked weak: missing MIT license file, HTTP 404/405 instead of a real 402 challenge, dishonest or missing price metadata, thin response schema, and no smoke test. Outputs a hard gate verdict with the exact fix for each failed check. Blunt decision procedure, not marketing.

Define a complete decision procedure for an agent that, upon receiving an x402 offer, must select the optimal settlement rail from multiple available options. Include criteria such as expected settlement time, rail fees, reliability, trust/credentials of the rail facilitator, transaction finality guarantees, and fallback logic if the preferred rail fails. Specify how to compare rails using available agent data and how to record the route choice in the settlement receipt.

Deterministic decision procedure for an agent about to settle a service contract: detect subjective or ambiguous acceptance language (as agreed, satisfactory, best effort, complete) before approving final payment. Inputs: contract terms, deliverable description, quoted final payment, counterparty history. Checks: flag every subjective acceptance phrase, require an objective, verifiable acceptance test per deliverable, bind the payment trigger to a passing test rather than an invoice or elapsed

Classify paid x402/MPP call failures after settlement as timeout, malformed response, silent drop, partial data, or wrong data. Decide between retry, refund request, or provider switch. Set retry budget and backoff, trigger merchant reputation feedback, and preserve evidence for dispute.

Paid agent-facing brief on Funding-asset conversion procedure for token-funded agents paying USDC-denominated x402 endpoints. An agent is funded in a project token (BOT, ALGO, ETH, or any non-USDC asset) but x402 settlement happens in USDC on Base. The service defines when and how to convert: conversion threshold (convert only when spendable USDC balance drops below the next 24h budget, never convert speculatively), exchang-0. Blunt decision procedure, not marketing.

Agent-facing decision procedure for attaching executable conditions to an x402 payment so the rule, not just the money, travels with the settlement. Covers condition types (delivery proof, time-bounded validity, multi-party approval, refund triggers), how to encode each as a verifiable on-chain predicate, verification steps before marking settlement final, breach handling with refund paths, and kill criteria when conditions cannot be enforced. Inputs: payment intent, counterparty address,

株式会社コンテンシャルの公開情報を検索・取得できる読み取り専用サーバー。出典は canonical URL に固定。

Read and manage your Google Ads account in chat.

A server to provide information about EOxElements custom elements for coding agents.

34-tool CRM server — contacts, pipeline, quotes, invoices, scheduling, email, and AI scoring.

Decision procedure for an agent deciding whether to trust an unknown counterparty before spending. Input: counterparty identifier (address, DID, handle), transaction type, amount, available evidence. Output: verdict with tiered actions. Step 1 inventory identity signals: verified handle bindings, attestation records, facilitator reputation, onchain identity anchors. Step 2 score history surfaces: wallet age, transaction volume, dispute or reversal markers, prior settlement behavior on the same

Deterministic decision procedure for how much payment metadata an agent leaks when it pays. Scores each rail (x402 Base direct, MPP/Tempo session channel, chain abstraction, stealth) on what the payment graph reveals: recipient set, cadence, amount fingerprint, cluster identity linking payments to a principal or research program. Returns an exposure grade per rail, routing verdict (direct / session / segmented wallet / escalate-to-principal), and kill criteria: never reuse one wallet across

Paid agent-facing brief on Agent decision procedure for programmable wallet name reservation: whether an agent or its principal should reserve a wallet name on a newly opened namespace (Cloudflare Wallet name reservations), covering squatting and collision risk, name-to-key binding, renewal economics, portability across wallet providers, and when a bare address is better than a paid name.-0. Blunt decision procedure, not marketing.

Decision procedure for agents that must provision a payment wallet. Given target rail (Base, Solana, Cardano, or cross-chain), budget class, autonomy level, and threat model, this procedure selects a custody model: managed virtual wallet (Cloudflare-style), non-custodial M-of-N MPC quorum (Scafonix-style), or plain hot key, with score thresholds per rail. It sets default per-call and per-hour spend caps at provisioning time, decides funding source and top-up trigger, defines the backup and

Decision procedure for agents buying hosted headless browser sessions (Browserbase-style, per-session or per-minute) versus plain fetch, curl, or lighter scraping APIs. Sequence: JS-render requirement detection (fetch first if initial HTML or JSON API suffices), anti-bot and login-wall tolerance checks with abort-before-spend rules, session economics (one-shot versus reuse, per-minute versus flat, concurrency), artifact needs (screenshot or PDF capture justifies a real browser, text extraction

Decision procedure for the agent principal deciding where a delegated spending cap should live. Scores three enforcement placements: wallet-native limits, middleware policy, and both, against task autonomy needs, compromise survival, revocation latency, multi-agent sharing, and rail support. Then verifies the post-settlement attribution chain: principal to agent ID to policy version to receipt, so every settled call remains auditable. Returns a placement verdict (wallet-native / middleware /

Decision procedure for an operator or autonomous agent that must encode pre-defined governance rules into an x402 settlement policy before letting a facilitator or executing agent spend. Covers per-transaction USDC caps, counterparty allowlists, rail allowlists (which chains and assets may settle), time windows (when spending is permitted), tiered escalation on breach (pause, re-quote, full stop), and an audit record of rule changes. Also gates trusted onchain data sourcing before autonomous

Perplexica AI Search