Genesis402

Get SEC company financials

genesis402_sec_financials

Fetch as-reported SEC financial fundamentals for a company by ticker or CIK, including revenue, net income, assets, and cash flow, without a data vendor.

Instructions

Paid ($0.01 USDC). As-reported fundamentals for one SEC filer from XBRL company facts. Use for quick fundamentals without a data vendor. For other SEC data search genesis402_catalog for "sec" and use genesis402_call. Give ticker or cik; one is required. Returns the latest annual and latest quarterly values for revenue, net income, operating income, total assets, liabilities, equity, cash, operating cash flow and diluted EPS, each with period end and filing date. Missing tags are marked unavailable, never estimated. Not investment advice. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, digits only, up to 10, e.g. 320193. Provide this or ticker.
`ticker`	No	Stock ticker, e.g. COIN or AAPL. Provide this or cik.
`payment_signature`	No	Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.4Sep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "also_accepted_networks": {
+      "description": "QUOTE_ONLY: every network the 402 challenge accepts.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "how_to_pay": {
+      "description": "QUOTE_ONLY: how to sign and resend the call.",
+      "type": "string"
+    },
+    "mode": {
+      "description": "QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.",
+      "enum": [
+        "QUOTE_ONLY",
+        "PAID",
+        "FREE"
+      ],
+      "type": "string"
+    },
+    "paid": {
+      "description": "true only when a payment was settled for this call.",
+      "type": "boolean"
+    },
+    "payment_required_b64": {
+      "description": "QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "atomic": {
+              "description": "Price in USDC atomic units (6 decimals), as a decimal string.",
+              "type": "string"
+            },
+            "network": {
+              "description": "CAIP-2 network id of the lane, eip155:8453 (Base).",
+              "type": "string"
+            },
+            "payTo": {
+              "description": "Address the payment settles to.",
+              "type": "string"
+            },
+            "usd": {
+              "description": "Price in US dollars.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "atomic",
+            "usd",
+            "payTo",
+            "network"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment."
+    },
+    "resource": {
+      "description": "QUOTE_ONLY: the full URL of the paid resource.",
+      "type": "string"
+    },
+    "result": {
+      "description": "PAID or FREE: the endpoint's JSON result."
+    },
+    "settlement": {
+      "description": "PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none."
+    },
+    "what_you_get": {
+      "description": "QUOTE_ONLY: the rail's description of what the payment buys.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "paid"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.3.3Sep 29, 2026

changedInput schema / properties / cik / description

Previous value: -"SEC Central Index Key (CIK), up to 10 digits. Provide this or ticker."New value: +"SEC Central Index Key, digits only, up to 10, e.g. 320193. Provide this or ticker."

changedInput schema / properties / ticker / description

Previous value: -"Stock ticker, e.g. AAPL or MSFT. Provide this or cik."New value: +"Stock ticker, e.g. COIN or AAPL. Provide this or cik."

Changed3 schema fields changedv0.3.2Sep 26, 2026

addedInput schema / properties / cik / description

Added value: +"SEC Central Index Key (CIK), up to 10 digits. Provide this or ticker."

changedInput schema / properties / payment_signature / description

Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."

addedInput schema / properties / ticker / description

Added value: +"Stock ticker, e.g. AAPL or MSFT. Provide this or cik."

First observedv0.3.1Sep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses the full payment protocol (first call for a quote with nothing charged, second call with signed payment for result and settlement), the exact price ($0.01 USDC), and data-integrity behavior ('missing tags are marked unavailable, never estimated'). This far exceeds what the readOnlyHint=false/openWorldHint=true annotations convey and does not contradict them.

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?

Front-loaded with price and purpose, and every sentence is substantive. Slightly penalized because the payment protocol is stated twice (top and bottom) and 'Not investment advice' is boilerplate.

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?

Complete for a paid, open-world data tool: purpose, alternatives, input requirements, enumerated return fields, missing-data policy, and payment mechanics are all covered, so nothing needed 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 value by clarifying the either/or requirement ('give ticker or cik; one is required') and by explaining the payment_signature two-step flow, which the schema documents only briefly.

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?

States a specific verb+resource: as-reported fundamentals for one SEC filer from XBRL company facts. It distinguishes itself from siblings by routing other SEC data needs to genesis402_catalog/genesis402_call, so an agent can pick it apart from the other genesis402_* tools.

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?

Gives explicit when-to-use ('quick fundamentals without a data vendor') and names the alternative path for other SEC data ('search genesis402_catalog for "sec" and use genesis402_call'). It also states the input requirement ('give ticker or cik; one is required').

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