> ## Documentation Index > Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt > Use this file to discover all available pages before exploring further. # Estimate the credit cost of a column run > Estimate the credit cost of an on-demand column run without running it. Takes the same request body as the run endpoint so estimate and run can never disagree about scope. Free runs (formula/manual columns) estimate to zero and are always sufficient. ## OpenAPI ````yaml /openapi.json post /tables/{table_id}/columns/{column_id}/run/estimate/ openapi: 3.1.0 info: contact: email: support@getoneprofile.ai name: Oneprofile Support description: >- REST API reference for Oneprofile, the GTM data layer for your CRM. Manage tables, enrichments, and integrations. Authenticate with an API key to get started. termsOfService: https://www.getoneprofile.ai/terms title: API Reference | Oneprofile version: '0.0' servers: - url: https://api.getoneprofile.ai security: [] tags: - description: Sender profiles, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - description: >- The LinkedIn channel: connecting an account to a sender, its safety limits and history, and the protocol the browser extension speaks. name: linkedin - description: 'The unified outreach inbox: threads, replies, labels, events.' name: inbox - description: 'The AI reply layer: workspace settings, drafts, and approval.' name: inbox-ai - description: Notification rules, per-user preferences, and the Slack connection. name: notifications - description: Endpoints for seeing all available integration types. name: integration-types - description: Endpoints for creating and managing integrations. name: integrations - description: Endpoints for the generic OAuth install/claim app-listings engine. name: app-listings - description: Endpoints for creating and managing API keys. name: apikey - description: Endpoints for managing billing and subscription information. name: billing - description: Endpoints for creating and managing tables. name: tables - description: Endpoints for table columns, formula previews, and on-demand column runs. name: table-columns - description: Endpoints for table rows and manual cell edits. name: table-rows - description: Endpoints for observing and cancelling table recompute runs. name: table-runs - description: >- Endpoints for org-shared per-column display preferences: hidden, pinned, width, and colour tint. name: table-ui-prefs - description: >- Endpoints for the org-shared names given to the column tint palette: what this organisation calls each colour. Org-level, not per-table. name: table-column-color-labels - description: >- Endpoints for the enrichment action catalog, model list, presets, draft generation, and saved agents. name: table-enrichments - description: >- Endpoints for teaching a saved agent from example rows: training sessions, per-row feedback, and the proposed prompt to approve. name: agent-training - description: >- The durable audit trail of a table's enrichment actions: configured, edited, run, cancelled, and settled cost. name: table-enrichment-audit-logs - description: Endpoints for saving and applying column templates. name: table-templates - description: Server-sent change feed for a table's grid. name: table-events - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.' name: table-views - description: >- The per-table AI Assistant: named conversations, the column suggestions a build turn produces, and the questions an analyze turn answers. name: table-assistant - description: >- Endpoints for PER-USER table preferences: favourites and recently opened. Unlike the rest of the table surface these are personal, so two members of one organisation legitimately see different answers. name: table-user-prefs - description: >- Endpoints for building a table from an uploaded CSV: upload and preview the inferred columns, commit the reviewed mapping, then poll the row load. name: table-imports - description: Endpoint for downloading a table's rows as CSV. name: table-export - description: >- Endpoints for the integration a table imports from: attach and preview it, promote imported fields into columns, and run the import on demand. name: table-sources - description: >- Endpoints for a table's recurring import cadence: set it, pause it, and read the next fire times. name: table-schedules - description: >- Endpoints for pushing a table's rows out to a connected integration: list writable destinations, derive their write capabilities, and map export columns. name: table-writeback - description: >- Endpoints backing a lookup column's setup: the connections whose records a column could read, and the identity fields one record type can be looked up by. name: table-integration-lookup - description: >- Endpoints for sourcing leads from the lead database: count and preview matches, land them in a table, and keep saved searches. name: find-leads - description: >- Endpoints for discovering a domain's subdomains from public certificate logs and landing the results in a table. name: find-subdomains - description: Endpoints for the credit balance meter and usage reporting. name: credits - description: >- Endpoints for the workspace referral program: the shareable link, the friends who joined through it, and claiming a code after signup. name: referral - description: >- Endpoints for the design partner program's customer surface: whether this workspace is a design partner, the badges its feedback has earned, and sending and reading that feedback. name: design-partner - description: >- Endpoints for the org-level AI business context — company description, ideal customer profile, buyer personas and interest signals — plus domain-based generation. name: ai-context paths: /tables/{table_id}/columns/{column_id}/run/estimate/: post: tags: - table-columns summary: Estimate the credit cost of a column run description: >- Estimate the credit cost of an on-demand column run without running it. Takes the same request body as the run endpoint so estimate and run can never disagree about scope. Free runs (formula/manual columns) estimate to zero and are always sufficient. operationId: estimate_table_column_run parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string - in: path name: column_id required: true schema: format: uuid title: Column Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TableColumnRunRequestSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/TableColumnRunEstimateResponseSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' description: Table column not found '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: Invalid request made to the API. '500': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Internal server error. '502': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Bad gateway error. '503': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Service unavailable. security: - HTTPBearer: [] - APIKeyHeader: [] components: schemas: TableColumnRunRequestSchema: description: Scope for an on-demand recompute of one formula column. properties: limit: anyOf: - maximum: 10000 minimum: 1 type: integer - type: 'null' description: Row count for scope=first_n (default 10). title: Limit offset: anyOf: - maximum: 1000000 minimum: 0 type: integer - type: 'null' description: >- Starting-row offset in display order for scope=first_n; omit to start at the first row. title: Offset record_id: anyOf: - format: uuid type: string - type: 'null' description: The target row for scope=cell; see also record_ids. title: Record Id record_ids: anyOf: - items: format: uuid type: string maxItems: 1000 type: array - type: 'null' description: >- The target rows for scope=cell — a swept selection re-runs in one request rather than one per cell. Wins over record_id when both are sent; scope=cell requires at least one of the two. title: Record Ids scope: $ref: '#/components/schemas/TableRunScope' description: 'Row scope: all | errored | unfilled | first_n | cell.' required: - scope title: TableColumnRunRequestSchema type: object TableColumnRunEstimateResponseSchema: description: >- Estimated credit cost of an on-demand column run, before running it. Free runs (formula/manual columns) estimate to zero and are always sufficient, even at a zero balance. The figure is an estimate: row counts and cell freshness can shift between estimating and running. properties: balance_sufficient: description: Whether the organization's available credits cover the estimate. title: Balance Sufficient type: boolean cells_total: description: All cells the run would compute, charged or not. title: Cells Total type: integer estimated_credits: description: >- Worst-case credit cost of the run (every waterfall rung runs) — the number the confirmation gate reasons about. title: Estimated Credits type: number expected_credits: default: 0 description: >- Expected credit cost under the waterfall resolution curve (80% of rows answer on the first rung, 95% by the second). Equal to estimated_credits when the run has no waterfall columns. Quote THIS to the user; charging is exact per row. title: Expected Credits type: number export_writes: description: >- Export columns this run would fire. Present so the confirmation can name the destination, the object and the action instead of only a row count. Empty for a run that writes nothing outside this table. items: $ref: '#/components/schemas/ExportWriteEstimateSchema' title: Export Writes type: array is_estimate: description: 'Always true: freshness and row counts can shift by run time.' title: Is Estimate type: boolean requires_confirmation: default: false description: >- True when the estimate crosses the confirmation threshold — ask before spending instead of running on first click. title: Requires Confirmation type: boolean rows_in_scope: default: 0 description: >- Rows the run would cover. This is what a scope choice is about, and what the credit estimate is derived from; `cells_total` also counts the dependent columns the run would recompute. title: Rows In Scope type: integer unit_price: description: >- Blended credits per charged cell (total estimate / units); 0 for free runs. title: Unit Price type: number units: description: Cells that would incur a charge (0 for free runs). title: Units type: integer required: - units - unit_price - estimated_credits - cells_total - is_estimate - balance_sufficient title: TableColumnRunEstimateResponseSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object ForbiddenResponse: properties: detail: description: The detail of why the request is forbidden. title: Detail type: string required: - detail title: ForbiddenResponse type: object NotFoundResponse: properties: detail: description: The detail of why the resource was not found. title: Detail type: string required: - detail title: NotFoundResponse type: object UnprocessableEntityResponse: properties: detail: description: >- The detail of the error. This is the error message to show to the user. You should also use the issues field to show more detailed error messages per field. Use this field for a single liner error message. title: Detail type: string issues: description: >- The issues that caused the error. There can be multiple issues. Each issue is a user-facing error message. items: $ref: '#/components/schemas/UnprocessableEntityIssue' title: Issues type: array required: - detail - issues title: UnprocessableEntityResponse type: object ServerErrorResponse: properties: detail: description: The detail of why the server returned an error. title: Detail type: string required: - detail title: ServerErrorResponse type: object TableRunScope: description: |- Row scope for an on-demand ``COLUMN_MANUAL`` run. ``CELL`` (a single row, origin-keyed so independent cell re-runs never terminate each other) rides the same enum as the column-lineage scopes. ``UNFILLED`` is "empty or out-of-date": errored, stale, valueless and never-computed cells — minus fresh deliberate skips, which would only skip again. enum: - all - errored - unfilled - first_n - cell title: TableRunScope type: string ExportWriteEstimateSchema: description: One export column the run would fire, and how much it would write. properties: action: description: >- create, update or upsert — what happens to records that already exist at the destination. title: Action type: string column_id: format: uuid title: Column Id type: string display_name: description: The export column's name, for the confirmation copy. title: Display Name type: string integration_type: description: Destination provider slug, e.g. 'hubspot'. title: Integration Type type: string record_type: description: Destination object written, e.g. 'contacts'. title: Record Type type: string rows: description: Rows this column would attempt to write. title: Rows type: integer required: - column_id - display_name - integration_type - record_type - action - rows title: ExportWriteEstimateSchema type: object UnprocessableEntityIssue: properties: input: anyOf: - type: string - type: integer - type: number - type: boolean - items: {} type: array - additionalProperties: true type: object description: The user's input that caused the error. title: Input loc: description: >- The location of the error. Always contains 1 or 2 elements. The first element is the type of location (e.g. 'body', 'query', 'path', 'header'). The second element is the name of the field that caused the error. If the error is not related to a specific field, the second element is not present. items: type: string title: Loc type: array msg: description: The message of the error. The error message to show to the user. title: Msg type: string type: description: >- The type of the error. Useful for frontend code to handle different types of errors. title: Type type: string required: - loc - msg - type - input title: UnprocessableEntityIssue type: object securitySchemes: HTTPBearer: scheme: bearer type: http APIKeyHeader: in: header name: X-API-Key type: apiKey ````