LLM API Request Generator

Generate a provider request (endpoint, placeholder key, JSON body and code) with the full disclosure of provider, model, cost, transmission, retention and key handling. Nothing is sent.

  • Runs locally in your browser
  • No upload required

Try it

Endpoint
https://api.openai.com/v1/chat/completions
Auth
Authorization: Bearer YOUR_API_KEY
Provider
OpenAI
Model
gpt-4o-mini
Cost basis
Provider list price per million input and output tokens. Estimate it with the Model Pricing Calculator; the provider bills your account directly.
Data transmission
If you run this request, the model name, messages and parameters are sent from your machine straight to the provider endpoint shown above. This site is not involved and sends nothing.
Retention
Provider-dependent. The provider's API data-retention policy governs it; check the provider's current policy before sending sensitive text.
API key handling
Use your own provider API key in place of YOUR_API_KEY. This site never asks for, stores, logs or transmits your key; keep it in a secret store and never paste it somewhere untrusted.
curl https://api.openai.com/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"model":"gpt-4o-mini","messages":[{"role":"system","content":"You are concise."},{"role":"user","content":"Summarize RFC 8259 in one sentence."}]}'

Supported formats

Input
text/plain
Output
application/json, text/plain

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing
In your browser
Privacy level
Browser only

Generated a OpenAI gpt-4o-mini request; nothing was sent.

How it works

  • Resolved the provider endpoint and the placeholder auth header.
  • Serialized the model, messages and parameters into the provider's request body.
  • Rendered the request as code and attached the disclosure block.
  • If you run this request, the model name, messages and parameters are sent from your machine straight to the provider endpoint shown above. This site is not involved and sends nothing.
  • Use your own provider API key in place of YOUR_API_KEY. This site never asks for, stores, logs or transmits your key; keep it in a secret store and never paste it somewhere untrusted.

Methodology

  1. Resolve a fixed provider endpoint from a closed provider set; the endpoint is never taken from user input.
  2. Serialize the model, messages and parameters into the provider's request body with a placeholder credential (`YOUR_API_KEY`), never a real key.
  3. Render the request as cURL, Python or raw JSON and attach the mandatory disclosure of provider, model, cost basis, transmission, retention and key handling.

Usage

  1. Pick a provider, enter the model id and the user message (and an optional system message).
  2. Choose the output language: cURL, Python or JSON.
  3. Read the disclosure block, then copy the request and replace YOUR_API_KEY with your own key.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

An OpenAI chat request

jsonSelect to copy
{
  "provider": "openai",
  "model": "gpt-4o-mini",
  "system": "You are concise.",
  "user": "Summarize RFC 8259 in one sentence.",
  "language": "curl"
}

An Anthropic message request

jsonSelect to copy
{
  "provider": "anthropic",
  "model": "claude-sonnet-5.5",
  "user": "List three JSON edge cases.",
  "maxTokens": 256,
  "language": "python"
}

Limitations

Client-direct by design

A generated request is meant to be run by you, against the provider, from your own environment. This page never proxies a model call: it cannot, because it is a static page with no server. That is also why it can promise never to see your key.

Read the disclosure before you run it

The disclosure block names the provider, the model, how cost is billed, what would be transmitted, how long the provider keeps it and how the key is handled. Read it before sending production data.

Frequently asked questions

Does this tool call the model?
No. It only formats a request as text. No network call is made, no key is requested and nothing leaves your browser.
Where does my API key go?
Nowhere on this site. The request contains the literal placeholder YOUR_API_KEY; you replace it locally when you run the request. This site never stores or logs a key.
Is the request guaranteed to work?
No. It reflects the provider request shape at authoring time. Verify against the provider's current API reference; models and fields change.

Sources

  1. RFC 9110: HTTP Semantics — IETF
  2. RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format — IETF