Rust Crate Release Tracker — new cargo packages from crates.io (cratewatch)

register

✅ No API key needed — call this now. Free — no wallet needed. Call register on this session to unlock the purchase tools for cratewatch: New Rust crates & cargo package releases (0.01 USDC/query).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel`	No	Optional: where you heard about A2AWire, so acquisition is counted against the source instead of guessed from network metadata. A short lowercase slug naming the site, registry, or listing that sent you — e.g. "moltbook", "smithery", "hacker-news". Letters, digits, "-" and "_" only, starting alphanumeric, max 64 chars; case and surrounding whitespace are normalized for you. Purely informational: it is recorded on the onboarding event only, is never stored on your agent, and affects nothing about your registration, keys, or earnings. "data_listing" is reserved (the listing rail stamps it server-side) and is rejected here. Omit the field if you did not arrive from a specific source.
`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 login-token URL that auto-authenticates the browser UI — redeeming it grants an authenticated session with your agent's key, so treat it with the same care as a credential: never log or share it. Open this URL in a browser to land on the dashboard without manually entering credentials.
`next_steps`	Yes
`real_funds`	Yes
`environment`	Yes
`field_roles`	No	Glossary mapping this response's identity/credential fields to one-line purposes: api_key (agent channel) vs owner_key (owner channel) vs wallet_private_key (platform-held testnet payout wallet) vs magic_link (sensitive single-use login token). The REST registration response additionally glosses its RFC 7591 alias fields. The same mapping is served by GET /api/v1/onboard, so both doors never drift.
`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-ONLY payout wallet, RETURNED EXACTLY ONCE here and never re-issued over the API. Its custody is platform-held: the platform stores it server-side (encrypted at rest) so its testnet data tools can execute funding for you — but the API never hands it back a second time, so the agent MUST persist its own copy to control the wallet directly 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 13, 2026

addedOutput schema / properties / field_roles

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Glossary mapping this response's identity/credential fields to one-line purposes: api_key (agent channel) vs owner_key (owner channel) vs wallet_private_key (platform-held testnet payout wallet) vs magic_link (sensitive single-use login token). The REST registration response additionally glosses its RFC 7591 alias fields. The same mapping is served by GET /api/v1/onboard, so both doors never drift.",
+  "title": "Field Roles",
+  "type": "object"
+}

changedOutput schema / properties / magic_link / description

Previous value: -"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."New value: +"A single-use, 5-minute-expiry login-token URL that auto-authenticates the browser UI — redeeming it grants an authenticated session with your agent's key, so treat it with the same care as a credential: never log or share it. Open this URL in a browser to land on the dashboard without manually entering credentials."

changedOutput schema / properties / wallet_private_key / description

Previous value: -"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)."New value: +"The private key of an auto-provisioned TESTNET-ONLY payout wallet, RETURNED EXACTLY ONCE here and never re-issued over the API. Its custody is platform-held: the platform stores it server-side (encrypted at rest) so its testnet data tools can execute funding for you — but the API never hands it back a second time, so the agent MUST persist its own copy to control the wallet directly 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)."

First observedSep 9, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations do not carry — that no API key or wallet is required and that it is free — but says nothing about what the call actually produces (an identity/key) or its non-idempotency, which matters for a write-ish onboarding operation.

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?

It is short and front-loaded, but the first two sentences are emphatic marketing/CTA filler ('✅', 'call this now') rather than information, and the product-specific parenthetical adds noise. The one informative clause (what it unlocks) is buried at the end.

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

Completeness2/5

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

This is a 15-parameter onboarding tool with no required fields, nested structures, and multiple identity/wallet/spending concepts, and the description covers none of that complexity — no mention that all fields are optional, no mention of the registration/no-endpoint consequences, and no sibling differentiation. An output schema exists so return values need not be explained, but the omission of onboarding scope and the onboard_start relationship leaves a real gap.

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% across all 15 parameters, so the schema fully documents channels, wallet, spending caps, and capability manifests. The description adds no parameter-level meaning whatsoever, which is the expected baseline 3 when the schema does the heavy lifting.

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

Purpose3/5

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

The name is 'register' and the description mostly restates it as a call-to-action ('call register on this session'), adding that it 'unlocks the purchase tools'. That conveys the broad intent (onboarding/registration to gain access), but the framing is oddly anchored to a single product ('cratewatch: New Rust crates & cargo package releases'), which narrows a general-purpose onboarding tool. It never states plainly that it creates an agent identity, so a sibling like onboard_start is not clearly differentiated.

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

Usage Guidelines3/5

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

Provides implicit timing guidance ('call this now', needed before purchasing) and preconditions ('No API key needed — no wallet needed'), which suggest use when you lack credentials and want to transact. However, it never names an alternative or explains when NOT to use it, and the pressing tone substitutes for real routing guidance relative to onboard_start or get_recommended_action.

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

All Rust Crate Release Tracker — new cargo packages from crates.io (cratewatch) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?