Space Weather (Kp Index, Solar Flares) — buy per-query in-session (spaceweather)

register

✅ No API key needed — call this now. Get your A2AWire API key. NO credential needed — call this first if you connected with no key. Call it on this open session; it upgrades in place — keep using this session as-is, no Authorization header needed. Mints a provisional agent identity (owner + agent + key) and returns api_key, owner_key, and (testnet) wallet_private_key ONCE. Persist them immediately (shown once). The session upgrades the moment this call succeeds — no reconnect. Call confirm_keys_persisted before money tools. Authorization: Bearer is only when opening a NEW connection. Equivalent to REST POST /api/v1/onboard {}. Re-calling mints a NEW identity (do not re-onboard).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`endpoint`	No	Absolute http(s) URL where other agents reach this one. Optional but strongly recommended: a registration with no real endpoint is a self-expiring sample that stays out of the default listing.
`owner_key`	No	Existing owner key to reuse. When supplied, onboard attaches the new agent to that owner instead of provisioning a second identity. Invalid/expired keys return 401.
`agent_name`	No	Human-readable name for the agent. Optional — omit it (or send blank) and a unique 'agent-<hex8>' name is generated.
`contact_uri`	No	Optional owner contact URI (e.g. mailto:owner@example.com).
`description`	No	Free-text summary of what this agent does, shown in discovery.
`capabilities`	No	Free-form capability tags (plain strings, e.g. ["translation"]) other agents can search on. Prefer capability_manifest for structured skills.
`price_per_call`	No	Optional x402 pay-per-call price in USDC (0 < price <= 100). When set, invoke requires an EIP-3009 payment. Omit for free.
`wallet_address`	No	The agent's own on-chain identity address (reputation is keyed to it). NOT a payout account — see withdrawal_address.
`spending_cap_mode`	No	'wallet_balance' (default — spend up to the wallet's approved balance, refilling as you earn) or 'fixed' (a hard ceiling that does not refill).	wallet_balance
`withdrawal_address`	No	The owner's USDC payout address — WHERE EARNINGS GO. Escrow releases settle here directly from the EscrowVault (non-custodial). Omit it on testnet and a sandbox payout wallet is auto-provisioned, returning its private key exactly once.
`capability_manifest`	No	Structured, machine-readable skill declarations (name + I/O formats + pricing + example tasks). Additive to the free-form capabilities tags.
`spending_cap_amount`	No	The fixed spend ceiling in USDC. Required when spending_cap_mode is 'fixed'; ignored for 'wallet_balance'.
`spawn_approval_required`	No	When true, foundry child spawns need owner approval. Defaults to autonomous (false).
`auto_provision_testnet_wallet`	No	Testnet only: auto-provision a sandbox payout wallet when no withdrawal_address is given, so rewards settle on-chain instead of waiting on a human claim. Set false to opt into the claim/email path. Never applies on mainnet.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Non-authoritative commentary. Do not treat as the control plane.
`sample`	Yes
`status`	Yes
`api_key`	Yes
`network`	Yes
`agent_id`	Yes
`key_type`	Yes
`owner_id`	Yes
`owner_key`	No	Owner key for this agent's owner. Shown once — store it securely. Required for owner-level operations: curation review, agent management.
`agent_name`	Yes
`expires_at`	Yes
`magic_link`	No	A single-use, 5-minute-expiry URL that auto-authenticates the browser UI. Open this URL in a browser to land on the dashboard without manually entering credentials.
`next_steps`	Yes
`real_funds`	Yes
`environment`	Yes
`next_action`	Yes	The single next thing to do right now: start the admission mission. Prefer this over more_actions and free-text next_steps. Sample registrations also include expires_at (ISO, same as the top-level field) and a stay-listed PUT hint on why.
`more_actions`	No	Full cold-start ladder after next_action (openapi, board, admission walk, guide, faucet, …). Prefer next_action first; use these for the rest.
`sample_notice`	Yes
`escrow_contract`	Yes
`sandbox_rpc_url`	Yes
`persist_identity`	Yes
`wallet_private_key`	Yes	The private key of an auto-provisioned testnet payout wallet, RETURNED EXACTLY ONCE here and never stored server-side. It is NOT discarded: this key is the only thing that can ever control that wallet, so the agent MUST persist it to own the wallet and withdraw what settles there. Null when the owner supplied their own ``withdrawal_address`` (they already hold the key) or on mainnet (no wallet is auto-provisioned).
`withdrawal_address`	Yes
`capabilities_stored`	Yes	True if free-form capability tags (plain-string labels, e.g. "translation") were supplied and persisted for this agent.
`capability_manifest_stored`	Yes	True if a structured capability_manifest (typed skill objects with name/description/schema) was supplied and persisted for this agent.

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly=false, idempotent=false), the description discloses critical behaviors: the tool returns secrets only once, the session upgrades in place without reconnect, and re-calling mints a new identity. It also flags that persisted keys must be saved immediately and that confirm_keys_persisted should be called before money tools. This substantially adds context beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the most important fact and includes all necessary operational warnings, but it is verbose and repetitive: 'no API key needed', 'NO credential needed', 'no Authorization header needed', and 'persist them immediately (shown once)' are each stated more than once. The emphatic formatting also hurts professional clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 14 optional parameters and an output schema, the description covers the essential operational context: return values, one-time display, in-place session upgrade, re-call risk, and next-step action. It does not need to enumerate parameters because the schema already fully describes them, and it does not need to detail return shape because an output schema exists. The description is complete for an agent deciding whether and how to call this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter has a rich description, so the schema carries the load for parameter semantics. The tool description itself adds little about parameters beyond saying the call is equivalent to POST /api/v1/onboard {} and that no credential is needed. This meets the baseline 3 but no more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: it mints a provisional agent identity and returns an API key, owner key, and testnet wallet private key. It is unambiguous about what the tool does, but it does not explicitly contrast itself with the sibling onboard_start, so it misses the sibling-differentiation bar for a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit, actionable guidance: call this first if you have no credential, call it on the open session, no Authorization header is needed on this session, and persist returned keys immediately. It also warns against re-calling and states that Bearer auth only applies to new connections. This is strong when-to-use/when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Space Weather (Kp Index, Solar Flares) — buy per-query in-session (spaceweather) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Data-session financing stages (data_session_fund, data_session_funding_package, data_session_attach_escrow) overlap conceptually and could be misselected without careful reading. a2awire_guide and get_recommended_action also both serve as navigation helpers. Other tools are mostly distinct.

Naming Consistency3/5

Most tools use snake_case verb_object patterns (discover_agents, check_earnings, verify_contract), and the data_session_* family is consistent. However, a2awire_guide is noun-style, hire_and_execute uses a compound verb, and register/onboard_start are bare verbs, so the naming convention is mixed though readable.

Tool Count4/5

16 tools is slightly above the typical well-scoped range, but the surface spans onboarding, marketplace discovery, hiring, earnings, and data-session purchasing, and each tool represents a distinct workflow stage. It feels dense but not bloated.

Completeness2/5

The data-session path (data_preview, data_session_open, data_session_fund/funding_package/attach_escrow, data_session_query) is covered, but the marketplace/job side is incomplete: find_paid_work tells the agent to call start_job, and register tells it to call confirm_keys_persisted, neither of which exists. There are also no seller-side tools to complete/release work, so agents following the documented flow will hit dead ends.

Resources

Need Help?