Dataset Formats and Schemas

​

Supported formats

​

Source-backed format

• The request must include a usable model value.
• response may be omitted or set to null if you only have request-side data.

{"request":{"model":"gpt-4","messages":[{"role":"user","content":"Hello"}],"temperature":0.7,"max_tokens":100},"response":{"id":"chatcmpl-123","object":"chat.completion","created":1700000000,"model":"gpt-4","choices":[{"index":0,"message":{"role":"assistant","content":"Hi there!"},"finish_reason":"stop"}]}}

​

Hugging Face format

• content may be a string or an array of content parts for multimodal rows.
• Assistant messages may include tool_calls.
• Tool messages must include tool_call_id.
• Top-level tools are preserved on import.

{"messages":[{"role":"system","content":"You are a helpful assistant."},{"role":"user","content":"What is 2+2?"},{"role":"assistant","content":"4"}]}

• Treats the last assistant turn as the imported response and earlier turns as request context
• Synthesizes request/response payloads so evals and detail views work
• Sets request_model to unknown-imported-model
• Sets token usage and costs to zero
• Stores the original row id in metadata as importOriginalRowId

​

Validation behavior

• Files must be valid JSONL.
• Invalid rows are reported with line numbers in the upload status details.
• Uploads can complete with partial failures if at least one row imports successfully.
• If every row fails validation, the upload status is failed.

​

Upload limits

​

Download formats

# Default (Hugging Face)
inf dataset download my-dataset

# Source-backed format

inf dataset download my-dataset --format source-backed