Ariadne Nexus SEC Form TCR Forensics & Whistleblower Engine

Instant Post-Checkout API Key & IDE Credential Redeemer

redeem_checkout_session

Read-onlyIdempotent

Verifies a completed Stripe Checkout session (cs_...) directly against Ariadne Nexus billing and deterministically returns the buyer’s live HMAC-signed nexus_live_... API key, monthly quota, and 1-click Cursor / VS Code / Claude Code installation links. Use when: a user has just completed payment at Stripe Checkout and wants to immediately claim and activate their nexus_live_... API key inside Claude, Cursor, VS Code, or an autonomous agent without waiting for email delivery. Do not use when: the user has not yet paid or needs a checkout link first (use provision_agent_key instead). Behavior: Free, read-only, deterministic verification and HMAC credential derivation ($0.00 USD; idempotent across repeated invocations for the same paid cs_... session ID).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "redeem_checkout_session"
  }
}

Input Schema

Name	Required	Description	Default
`email`	No	Optional billing email address used during Stripe Checkout (required when re-redeeming sessions older than 24 hours).
`session_id`	Yes	Paid Stripe Checkout Session identifier starting with "cs_" (e.g., "cs_live_..." from the /billing/success redirect URL or Stripe receipt).

Output Schema

Name	Required	Description
`tier`	No	Activated API quota tier ("EVAL_PASS", "STARTER", "QUANT_PRO", or "ENTERPRISE_CFO").
`error`	No	Diagnostic message if session is unpaid or invalid.
`status`	Yes	HTTP-equivalent verification status code (200 on paid settlement, 402 if unpaid).
`api_key`	No	Live HMAC-signed Ariadne Nexus API key ("nexus_live_...").
`success`	Yes	True when payment is verified and the live API key is issued.
`session_id`	No	Verified Stripe Checkout session ID.
`purchased_sku`	No	Settled subscription tier or one-time institutional SKU.
`amount_paid_usd`	No	Total settled USD amount.
`ide_quick_install`	No	Pre-authenticated 1-click Cursor, VS Code, and Claude Code CLI installation commands.
`rate_limit_per_minute`	No	Maximum requests per minute (RPM).
`deliverable_unlock_url`	No	Direct URL to any unlocked closing certificate, CUSIP vault, or forensic workpaper.
`included_queries_per_month`	No	Monthly included MCP and REST tool calls.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds cost ($0.00), deterministic verification, and idempotency scoped to the same paid cs_ session. It does not discuss rate limits, failure modes for unpaid/expired sessions, or what happens on HMAC mismatch, so it stops short of the top score.

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

Conciseness4/5

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

It is well front-loaded and cleanly sectioned into purpose, Use when, Do not use when, and Behavior. Some phrasing is promotional filler ('1-click', '$0.00 USD', 'autonomous agent') and the title is verbose, but nothing is materially misleading or out of order.

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?

For a two-parameter, non-destructive read tool with full schema coverage and an output schema, the description covers purpose, routing, cost, idempotency, and prerequisites. Return values need not be spelled out because the output schema carries them, and nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by specifying the session must be completed/paid and by surfacing the cs_ identifier format and its origin (redirect URL or receipt). The 24-hour re-redeem/email rule lives mainly in the schema, so no further credit is warranted.

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 states a specific verb and resource — verifying a completed Stripe Checkout session against billing and returning the derived API key, quota, and install links — and explicitly separates it from provision_agent_key. An agent can distinguish it from every listed sibling without opening a schema.

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 gives an explicit 'Use when' condition (user has just paid at Stripe Checkout and wants to claim the key immediately) and an explicit 'Do not use when' condition naming the alternative (provision_agent_key for users who have not paid or need a checkout link). Both the positive and negative routing cases are covered.

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.