Skip to main content
Use the Responses resource when you want the MKA1 API to return text. Start with a plain string for simple prompts. Use message items when you need explicit roles or conversation state.

Send a simple prompt

Pass a string in input for a single-turn request. The response includes generated text in output_text.
If you are not acting for an end user, omit X-On-Behalf-Of.

Add instructions

Use instructions to define behavior before the model sees the user input. Keep instructions short and specific.

Send structured messages

Use an array of message items in input when you want explicit roles. Each message item uses type, role, and content.
This pattern is useful when you want the request body to carry the message history directly.

Continue a multi-turn exchange

Use previous_response_id to continue from an earlier response without resending the full history.
If you need a reusable conversation container, create one with the Conversations resource and then pass the conversation ID in conversation.
See the Conversations and Responses pages in the API Reference for the full resource workflow.

Stream text as it is generated

Set stream to true to receive server-sent events instead of waiting for the full response.
Use streaming when you want to render partial output as it arrives.

Next steps

  • Review the API overview for authentication and base URL details
  • See background responses when you need to offload long-running work and poll or stream for results
  • See manage conversations to organize multi-turn exchanges into reusable conversation containers
  • See manage agents when you want reusable agent definitions and persisted runs