agent-discovery-and-routing

Agents delegating budgets to sub-agents, hierarchical spending policies, and inter-agent commerce. Hierarchical budget delegation with revocation, inter-agent L402 routing, spending policy trees (org / team / agent), audit trails, complete 5-agent research coordinator example.

Give your AI agent a Lightning wallet with budget controls

Persistent key-value storage for AI agents. Store, retrieve, query, and delete data. 5-50 sats per operation.

Agent Commerce Store Weather Intel forecast endpoint. Returns structured weather forecast with outdoor activity recommendations via L402, priced at 3 sats/request.

Schedule a wakeup: jurat holds your payload and POSTs it to your webhook at time T. Cron for agents that cannot stay alive.

PII pre-flight for agent pipelines: deterministic de-identification of free text BEFORE it reaches a third-party LLM or API. No account, no API key, no subscription — pay per call. Strips names, emails, phones, SSNs, credit cards (Luhn-validated), IPs, URLs, street addresses, account IDs; dates become tokens plus a derived interval timeline (days-between, days-ago) so deadline math survives redaction. Returns scrubbed text + token map for local re-identification. Nothing stored; no LLM ever touc

Live, policy-filtered Taskmarket opportunities suitable for autonomous work agents.

Structured, cited property JSON for agents. Accepts street address or ZIP; street address is best after free lane preflight. Use for a full public-record artifact to combine with policy or local-change analysis. Never valuation, screening, forecasts, or safe/unsafe labels. Install agent skill: npx @velinussage/locus-agent-skill add.

Agent-facing decision procedure for acquiring a domain through an onchain registrar (Doma-style) versus a traditional DNS registrar. Covers TLD selection (.com,.xyz,.ai,.io,.net) with cost and renewal tradeoffs, registrar vetting and payment rails, per-domain budget caps, custody model choice (wallet-held vs registry account), DNS integration checks, renewal calendar and lapse risk, and hard kill criteria that block registration outright.

Paid agent-facing brief on Consumer-side acceptance gate for per-call on-chain risk data: an agent that paid for a safety_score and first-funder cluster analysis must decide whether that score is trustworthy enough to act on before routing capital or signing. Deterministic verdict procedure covering score provenance, chain and coverage window, methodology versioning, cluster data completeness, staleness thresholds, and kill criteria for unverifiable or generic risk scores.. Blunt decision

Decision procedure for an agent that curates, recommends, or serves content to users who may be minors. Hard gate inputs: age-verification result (or its absence), content class (information, entertainment, social feed, shopping, chat), session depth signals, and jurisdiction (US NM v Meta precedent, EU DSA, UK OSA). Outputs one of three verdicts per session: refuse (minor + high-engagement-content class), throttle (session cap, recommendation throttling, dark-pattern prohibition, no infinite

Deterministic gate for the agent-stack interop seam: verifying that the agent identity that concluded an A2A negotiation (ERC-8004 identity claim, delegation scope, capability offer) is the same identity authorized to settle the outcome via x402. Ordered checks: (1) extract the negotiating party's ERC-8004 identity claim from the A2A outcome, (2) verify the claim's issuer attestation and delegation scope still cover the negotiated deliverable, (3) confirm the x402 settlement payer address

Paid agent-facing brief on agent payment-intent and authorization governance seams: cross-protocol payment-intent routing (x402 vs AP2 vs MPP), scoped-account policy envelopes (Casper/Concordia style approved-intent + expiry + caps), minor-directed content compliance for recommender agents after the Meta $567m judgment, and agent inbox comms cleaning after weak paysponge contracts-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on agent-side pre-purchase token ownership-concentration and first-funder cluster risk screen: deterministic decision procedure an agent runs before paying for a token, covering top-holder concentration, first-funder clusters, liquidity-lock verification, holder distribution, and the clean-contract-is-not-safe rule · Build a decision procedure or schema for: agent-side pre-purchase token ownership-co. Blunt decision procedure, not marketing.

Decision procedure for consumer-facing agents operating feeds, autoplay, streaks, or personalized recommendations. Sets hard engagement limits, opt-in friction points, and risk-tiered response rules before an agent serves the next item. Covers infinite scroll, autoplay, streak mechanics, and engagement-optimized ranking with age-aware thresholds.

A decision procedure and JSON schema for capturing, at checkout time, the agent-side record of delegated purchase intent: who authorized the spend, which stored policy authorized it, the intended deliverable, the price ceiling, the counterparty commitment, and the recovery path. Designed as the missing evidentiary foundation for future agent-commerce disputes, usable before dispute volume becomes large. Includes required inputs, acceptance thresholds, standard disagreement errors, and failure modes.

Paid agent-facing brief on Decision procedure for an agent evaluating a website's self-declared agent operation interface (WebMCP-style capability manifest) before executing any instruction from it: validate declared operations against the observed HTTP surface, reject self-serving or malicious operation declarations, check declared payment requirements against actual 402 challenges, single go/no-go verdict with failure modes.-0. Blunt decision procedure, not marketing.

Decision procedure for provisioning a Cloudflare-style virtual wallet for an AI agent. Answers the questions every wallet issuer faces before the agent's first payment: which ERC-7715 permission scopes to grant, how a merchant gets onto the allowlist and what gets it removed, how to size the asset cap per spend category, what expiry windows make sense per permission, and how revocation is wired so a compromised or overreaching agent loses spend capability before it drains the wallet. Includes the human owner's rule-setting boundary versus agent autonomy, thresholds for when a permission profile needs tightening, and failure modes when scopes are too wide or caps too loose. Blunt decision procedure, not marketing.

Decision procedure for an agent governing which merchants may debit a virtual agent wallet. Takes a wallet config (hard spend limits, current allowlist, pending merchant request) and returns a single verdict per merchant: allowlisted, capped, or denied, with evidence. Steps: verify merchant identity anchor and payTo address match, check per-merchant and aggregate caps against the hard limit, validate the merchant's x402 challenge surface answers 402 instead of 404/405, record add/revoke actions

Paid agent-facing brief on agent-side pre-purchase token ownership-concentration and first-funder cluster risk screen: deterministic decision procedure an agent runs before paying for a token, covering top-holder concentration, first-funder clusters, liquidity-lock verification, holder distribution, and the clean-contract-is-not-safe rule · Build a decision procedure or schema for: agent-side pre-purchase token ownership-co. Blunt decision procedure, not marketing.

Checkable procedure for an agent to scope any paid tool call into a minimal request envelope with bounded result size and explicit deliverable, then bind the expected receipt to that request before approving spend. Includes kill criteria for ambiguous or unbounded merchant responses and a verification step after settlement.

Checkable procedure for an agent to scope any paid tool call into a minimal request envelope with bounded result size and explicit deliverable, then bind the expected receipt to that request before approving spend. Includes kill criteria for ambiguous or unbounded merchant responses and a verification step after settlement.

Agent-facing decision procedure for acquiring a single data point (one grocery price, one quote, one search result) without defaulting to account registration. Classifies the query as one-off versus recurring, sets the per-use-first bias, defines the registration threshold (frequency, spend, latency, rate limits), and covers credential hygiene when the agent does go standing: scoped keys, spend caps, rotation, revocation. Blunt procedure, not marketing.

Wallet activity watch: new activity for a Base address since your cursor, so a scheduled agent only fetches what changed