finalize_upload
Turns the file you sent into an import: reads it out of storage, analyzes it, de-identifies it, and returns the column metadata, the CSV workspace connection id to build a model on, and the next steps, in the same shape upload_csv returns. The raw file is discarded as soon as it has been read. Safe to call twice: a second call reports the stored import and re-reads nothing. If the file never arrived it says so, and the address is still good.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
import_id | string | Yes |
What it returns
The column metadata ax1om read from the uploaded file, the id of the CSV workspace connection the upload feeds, and the next steps to create a model on it.
Credential
An app session token, from an authenticated app.ax1om.ai session. Call it with only an API key and you get a plain refusal saying so, rather than a confusing 401.
Network call: yes. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call finalize_upload: turns the file you sent into an import: reads it out of storage, analyzes it, de-identifies it, and returns the column metadata, the CSV workspace connection id to build a model on, and the next steps, in the same shape upload_csv returns.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "finalize_upload", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.