Skip to main content
Up to 25 reporting persons and their separately reported share counts and class percentages. Joint filers may report overlapping interests. Operation ID: ownership.beneficial_13dg. Family: Deals & Transactions. Read the live operation contract (JSON) for the current input and output schemas, price, limits and required scopes. Status: Available (AVAILABLE). Supported interfaces: REST, MCP. Commercial status: Available. Receive the structured result and receipt in Console after the run settles. Execution interfaces: UI, REST, MCP.

When to use it

Check how much of an issuer’s security class each reporting person disclosed in one structured Schedule 13G or amendment. Joint filers can report the same shares.

Price and billing unit

Request a quote for one schedule 13G beneficial ownership. Review its inputs, delivery plan, use terms and maximum charge before accepting. Retrying the same purchase uses the same idempotency key. Price: $0.10. Billing unit: per successful delivery. Charge condition: The authorized execution delivers a validated result and settles once. Failed pre-settlement executions are not charged; reservation release must be confirmed. Retrieve the same run if charge state is uncertain. Execution budget: Maximum $0.10 per accepted execution. Fund your Console wallet, review the quote and approve the charge before execution.

Inputs

Subject issuer CIK and exact structured Schedule 13G accession

Result and output schema

Up to 25 reporting persons and their separately reported share counts and class percentages. Joint filers may report overlapping interests.

Examples

Illustrative request and result for this scope. The names, values and record references are examples. Actual delivery depends on the published availability and agreed scope.

Example input

Example structured output

API example and execution

Verified production contract · Base URL: https://console.altss.com/v1/console. Quote first. Obtain explicit approval of the price, plan and use terms before sending accept:true. Reuse the same purchase idempotency key on retries. Required scope: company.read. Organization authority, funding checks and spending limits apply to paid execution. Supply credentials in the documented authorization header. Replace a placeholder run ID with an actual authorized run ID.
This example requests a quote. A paid run requires the unchanged returned quote, explicit acceptance and a stable idempotency key.

MCP and A2A

Supported interfaces: REST, MCP. Current MCP tools: altss_quote, altss_run, altss_get_run. Inspect tools/list and inputSchema before use. Paid A2A execution is unavailable. The separate anonymous A2A reader serves public information. REST guide · MCP guide · A2A scope · Authentication and credentials

Sources, evidence and freshness

  • Public records and official sources
Retain source attribution, observation and event dates, evidence and explicit unknowns where supplied. A record update is not independent verification. Historical source collection dates describe when the material was observed. Coverage and freshness depend on each returned source. Preserve its observation date and use restrictions with the result.

Limits and permitted use

  • Includes: Get up to 25 reporting persons, shares and separately reported class percentages from an exact structured Schedule 13G or amendment. Joint filers may report overlapping shares.; Official filing citations and retrieval times. Excludes: Contact details; Security identifier directories; Investment advice. Requires scope company.read. Source: public registry.
  • A timeout does not establish the final charge. Retrieve the existing run before retrying.
Use is limited by the accepted quote or agreed delivery scope, source restrictions and privacy controls. Storage, attribution, retention, redistribution and training permissions do not expand through normalization.

Next step

Try Console · Open Console workspace · View the capability on Altss · Wallet and billing Back to Deals & Transactions · All capabilities · Price schedule