Skip to main content
Run one capability over every row of a table; each row is charged at that capability’s price and only for successful rows. Operation ID: table.run_column. Family: Platform tools. Status: Available (AVAILABLE). Supported interfaces: REST, MCP. Commercial status: Supporting tool. Run selected cells and open the receipt for each delivered result. Execution interfaces: UI, REST, MCP.

When to use it

Choose a Workbench recipe, import your rows and review the maximum price before you run the batch. Each delivered cell has its own source and receipt.

Price and billing unit

Preview the cost and set a spending limit. Each successful cell uses its capability’s price. Price: Selected capability price. Billing unit: per successful row, at the capability price. Fund your Console wallet, review the quote and approve the charge before execution.

Inputs

Table, column recipe, capability id

Result and output schema

Filled column with per-row receipts

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. Estimate the selected cells and authorize a maximum spend before execution. Each successful result uses the selected capability price. Supply credentials in the documented authorization header. Replace a placeholder run ID with an actual authorized run ID.

MCP and A2A

Supported interfaces: REST, MCP. Current MCP tools: altss_table_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

  • Organization-scoped platform activity
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

  • Organization-scoped credentials and current permitted-use terms apply.
  • Re-reading a result does not create a new purchase.
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

Open Intelligence Tables · Open Console workspace · View the capability on Altss · Wallet and billing Back to Platform tools · All capabilities · Price schedule