Completions

Completions endpoints send messages to deployed Pickaxes and Agents.

Endpoints

POST /completions

Send a message to an API deployment programmatically. Use the deployment ID as the Bearer token in the Authorization header.

• Full URL: https://api.pickaxe.co/v1/completions

Request Fields

• message (string, optional): Use this for chat-style API deployments. This is the message sent to the deployed Pickaxe or Agent.
• inputs (object, optional): Use this for form-style API deployments. Provide key-value pairs that match the deployment's input fields. These keys are deployment-specific. For the real field IDs, check the deployment's API preview. Example: { "your_input_field_id": "value" }
• userId (string, optional): The identifier used to track the user making the request. If omitted, IP address tracking is used instead, which may be less reliable because multiple people can share the same IP address.
• conversationId (string, optional): A custom identifier used to preserve conversation context across requests. If omitted, a random conversation ID is generated automatically.
• imageUrls (string[], optional): Optional image URLs to include in the request for supported multimodal models. Each URL must begin with "https://" and end with a supported image extension such as .png, .webp, .gif, .jpg, or .jpeg.
• stream (boolean, optional): If true, the response is streamed back in real time using Server-Sent Events (SSE). Otherwise, the API returns a single JSON response. Defaults to false.

Examples

curl -X POST https://api.pickaxe.co/v1/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_DEPLOYMENT_API_KEY" \
-d '{
  "message": "Hello, how can I help you?"
}'