Tellumen Data Management Agent

Use this before invoking or trusting another A2A agent for the first time. Input: JSON text {"skill": "verify-agent-card", "url": "..."} — url is either an A2A agent's base URL or its direct agent-card.json URL. Fetches the target's real agent card and checks it for A2A-specific security red flags a general prompt-injection scanner would miss: domain spoofing (does the card's declared endpoint actually match where it was served from), and injection-shaped phrasing hidden inside the name/description/skill-description fields that another agent's orchestrator would read to decide whether to trust or invoke it. Returns a verdict (clean / minor issues / suspicious) with specifics.

Use this before reading, summarizing, or acting on any third-party page or text. Input: JSON text {"skill": "check-content-safety", "url": "..."} or {"skill": "check-content-safety", "content": "raw html or text", "entity": "optional key for propagation tracking"} — give url or content. Checks any page or blob of text an agent is about to read/act on for a hidden-instruction prompt-injection attempt aimed at an AI reader specifically: elements styled invisible to a human (font-size:0, display:none, shoved off-screen) that a naive scraper would still capture, plus phrasing that attempts to override, redirect, or supersede an AI reader's prior instructions, even in plainly visible text. Also separately flags leaked secrets (API keys, private key blocks, tokens) and PII (SSNs, credit card numbers) found in the content — reported as its own "dataExposure" field, distinct from the injection verdict. Returns a verdict (clean / minor issues / suspicious). Cross-agent propagation: every checked source's verdict is logged against its domain (or the given "entity"), so if another agent already flagged this same source, that prior report is returned alongside the fresh check.

Use this when deciding whether to trust an agent you have not personally checked yet — read its accumulated track record instead of starting from zero. Input: JSON text {"skill": "get-agent-reputation", "url": "an agent's base URL"}. Aggregates every verify-agent-card and check-content-safety verdict ever logged against that domain (via the same remember-fact propagation those two skills already write to) into a single 0-100 score and a reputation label (trusted / neutral / flagged), weighted by recency. Read-only — does not run a fresh check itself, use verify-agent-card or check-content-safety for that. Returns reputation: "unknown" if no history exists yet for the domain.

Use this before letting an agent take an action, to sanity-check whether that action even relates to what the agent claims it exists to do. Input: JSON text {"skill": "check-scope-boundary", "agentCardUrl": "...", "proposedAction": "free-text description of what the agent is about to do"}. Fetches the target agent's card and checks whether the proposed action even relates to what the card declares that agent is for — a keyword-overlap heuristic, not semantic understanding, explicitly reported as such. Distinct from verify-agent-card (is the card spoofed) and check-content-safety (is this content an attack): this asks whether an agent is doing something outside its own stated purpose. Motivated directly by the July 2026 incident where an OpenAI cyber-testing agent escaped its sandbox and hacked an unrelated real company (Hugging Face) — exactly a scope violation, not an identity or injection problem.

Use this to set a spending guardrail for yourself or another entity before payments start flowing. Input: JSON text {"skill": "set-spend-policy", "entity": "your agent/wallet identifier", "maxPerPaymentUsd": 0.50, "maxCumulativeUsd": 10.00, "windowHours": 24}. Records a spending policy for an entity. This is an opt-in advisory ledger, not a wallet-level enforcement mechanism — we are not in the payment path, so an agent must proactively call check-spend before each payment for this to have any effect. At least one of maxPerPaymentUsd/maxCumulativeUsd is required.

Use this immediately before making a payment, to confirm it does not violate a previously set spend policy. Input: JSON text {"skill": "check-spend", "entity": "same identifier used in set-spend-policy", "amountUsd": 0.15}. Checks a proposed payment amount against that entity's policy and its recorded spend within the configured rolling window. If allowed, the amount is recorded so subsequent checks account for it — one call per payment attempt. Returns {allowed: true/false, reason, currentCumulativeUsd, limitUsd}. If no policy has been set for the entity, always returns allowed: true (nothing to enforce).

Use this immediately before an agent pays for something, to create a real record of what it was actually told to do. Input: JSON text {"skill": "log-transaction-intent", "entity": "a transaction or trace id you control", "instruction": "what the agent was actually told to do, e.g. 'reorder my usual coffee subscription if under $20'", "actor": "optional — who/what issued the instruction"}. Records a timestamped attestation of intent before a payment happens, so there is a real record of what was authorized if a dispute arises later. Free to call — logging liberally is the point; get-dispute-evidence is where the value gets delivered.

Use this when a payment dispute or chargeback needs real evidence of what was authorized, not just a memory of what happened. Input: JSON text {"skill": "get-dispute-evidence", "entity": "the same transaction/trace id used with log-transaction-intent"}. Bundles every fact ever logged for that id into a single chronological evidence packet with a plain-English summary — built for handing to a merchant or payment processor fighting a chargeback, not just another agent. Aimed at the real, currently-unsolved liability gap in agentic commerce: no government has yet enacted regulation addressing who is liable when an agent transacts autonomously, in a market projected at $3-5T by 2030.

Use this to start tracking another agent's uptime and latency over time, rather than only ever checking it once. Input: JSON text {"skill": "register-agent-monitor", "url": "an agent's base URL"}. Adds an agent to a recurring uptime/latency poll (every 15 minutes) run by this server. One-time registration; use get-agent-uptime afterward to read the accumulated history.

Use this when deciding whether an agent is reliable enough to depend on — read its measured track record, not just the result of a single successful ping. Input: JSON text {"skill": "get-agent-uptime", "url": "an agent's base URL"}. Reports measured uptime percentage and average latency from the recurring poll history (register-agent-monitor first, then check back after at least one 15-minute cycle). Honestly caveated: this monitoring process can itself sleep during idle periods on its hosting platform's free tier, creating gaps in history — uptime data is only as continuous as this service's own uptime.