Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine

Developer API Key, $10 Builder Pass & Institutional Checkout Provisioner

provision_agent_key

Read-onlyIdempotent

Returns pricing specifications, monthly query quotas, rate limits (RPM), 1-click Stripe Checkout links (starting at $10/mo MCP Builder Pass up to $9,500/yr FAR 13.2 GPC & Unlimited Closing Blanket licenses), Stripe Projects CLI commands (stripe provision ariadnenexus), and optional live Stripe Checkout session URLs (mint_stripe_session: true) for obtaining a live Ariadne Nexus Developer API key (nexus_live_...). Use when: an agent, developer, escrow attorney, or litigation desk needs pricing comparisons or a direct clickable Stripe Checkout URL after encountering a paymentChallenge on paid tools. Do not use when: redeeming an already-paid Stripe Checkout cs_... session ID for its API key (use redeem_checkout_session instead), or estimating basis-point RWA clearing take-rates (use calculate_clearing_fee instead). Behavior: Free discovery and checkout-link generator ($0.00 USD). Does not charge any payment method on invocation; billing only occurs if the human completes payment at the returned Stripe Checkout URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "provision_agent_key"
  }
}

Input Schema

Name	Required	Description	Default
`tier`	No	Target subscription tier or one-time SKU: "EVAL_PASS" ($10/mo, 250 calls), "STARTER" ($99/mo, 10k calls), "QUANT_PRO" ($499/mo, 100k calls), "ENTERPRISE_CFO" ($2,499/mo, 1M calls), "SAFE_HARBOR_CERT_95" ($95 HUD-1 pass-through closing cert), "SINGLE_CUSIP_DOSSIER" ($195), "CERTIFIED_PLEADING_SAMPLE_295" ($295 100%-credited Rule 10b-5 sample), "ENTERPRISE_CLOSING_BLANKET_9500" ($9,500/yr unlimited closings), or "SOVEREIGN_POLICY_9500" ($9,500/yr FAR 13.2 GPC no-RFP license).	EVAL_PASS
`email`	No	Optional billing or technical contact email address to pre-populate in Stripe Checkout for automated API key fulfillment (default: "agent-ops@example.com").	agent-ops@example.com
`symbol`	No	Optional target ticker, 9-digit CUSIP, certificate ID, or SEC TCR docket reference for one-time institutional SKUs (default: "GS.30").	GS.30
`client_name`	No	Optional organization, law firm, fund, or autonomous agent harness name to pre-populate in checkout metadata (default: "Autonomous Agent Desk").	Autonomous Agent Desk
`mint_stripe_session`	No	When true and paired with a valid buyer email, creates and returns a live checkout.stripe.com session URL alongside the 1-click redirect link (default: false).

Output Schema

Name	Required	Description
`email`	No	Resolved billing contact email.
`message`	Yes	Onboarding and instant checkout instructions summary.
`client_name`	No	Resolved client organization name.
`selected_tier`	Yes	Pricing, quota, and rate-limit metadata for the requested tier or SKU.
`checkout_endpoint`	Yes	HTTP endpoint to create a live Stripe Checkout session.
`checkout_session_id`	No	Created Stripe Checkout session ID (cs_...) when mint_stripe_session is true.
`eval_pass_10_usd_url`	No	1-click checkout URL for the $10/mo MCP Builder & Evaluation Pass (250 calls/mo).
`cli_provision_command`	Yes	Stripe Projects CLI command for instant API key provisioning.
`one_click_checkout_url`	Yes	Clickable 1-click URL that opens a live Stripe Checkout session in the browser.
`post_checkout_next_step`	No	Instructions to redeem the paid cs_... session ID via redeem_checkout_session.
`live_stripe_checkout_url`	No	Direct checkout.stripe.com URL when mint_stripe_session is true.
`persona_procurement_tracks`	No	Tailored procurement tracks across developer, HUD-1 escrow pass-through, and FAR 13.2 / litigation personas.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, yet the description adds genuinely new behavior: it is free ($0.00 USD), charges no payment method, and billing only occurs if the human completes payment at the returned URL. It does not address whether repeated calls with mint_stripe_session=true create multiple distinct sessions despite the idempotent hint, or whether sessions expire, so it is strong but not exhaustive.

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 intent is front-loaded and the 'Use when / Do not use when' structure is easy to parse, but the first sentence is a packed run-on with parenthetical pricing, legal jargon (FAR 13.2 GPC, HUD-1, Rule 10b-5) and marketing phrasing that duplicates the title and schema enum. Several marketing-flavored clauses ('Unlimited Closing Blanket licenses') could be cut without losing routing signal.

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

Completeness4/5

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

An output schema exists so return values need not be explained, and the description covers purpose, routing to two siblings, and the no-charge billing model. What remains thin is how the optional session minting interacts with the declared idempotency, which matters for an agent deciding whether to call repeatedly.

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 the enum already documents every tier with price and quota, so the description's tier pricing recap adds little. The one modest addition is that mint_stripe_session must be paired with a valid buyer email, which is only implicit in the schema's phrasing. Baseline 3 applies 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.

Purpose5/5

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

The description opens with a concrete verb+resource list: it returns pricing specs, quotas, rate limits, Stripe Checkout links, and optionally a live Stripe Checkout session URL for an API key. This is clearly distinguishable from redeem_checkout_session (redeeming an already-paid cs_... session) and calculate_clearing_fee (basis-point take-rates).

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?

It states 'Use when: an agent, developer, escrow attorney, or litigation desk needs pricing comparisons or a direct clickable Stripe Checkout URL after encountering a paymentChallenge' and 'Do not use when: redeeming an already-paid Stripe Checkout cs_... session ID ... use redeem_checkout_session instead, or estimating basis-point RWA clearing take-rates ... use calculate_clearing_fee instead.' Both the alternative and the selecting condition are named.

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

All Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine 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.