Use cloud backends

Use a cloud backend when you want hosted inference instead of the local llama-server backend. This page is a provider setup recipe; see the backends reference for canonical model, URL, credential, concurrency, and call-cap requirements. Each provider needs an API key in the environment; ajq does not read API keys from config.toml.

Use Anthropic Claude

1. Export an Anthropic API key:

   export ANTHROPIC_API_KEY="sk-ant-..."
   

2. Run a semantic query with --cloud:

   printf '{"msg":"urgent billing issue"}' \
     | ajq --cloud --model haiku '.msg =~ "urgent"'
   

   --cloud is the same as --backend anthropic. Model aliases and the default model are listed in the backends reference.

3. If the key is missing, ajq stops before contacting the provider:

   ajq: error: anthropic backend API key is empty; set ANTHROPIC_API_KEY
   

Use OpenAI

1. Export an OpenAI API key:

   export OPENAI_API_KEY="sk-..."
   

2. Choose an OpenAI model explicitly:

   printf '{"msg":"urgent billing issue"}' \
     | ajq --backend openai --model gpt-4o-mini '.msg =~ "urgent"'
   

3. If you use an OpenAI-compatible proxy, pass its API root with --base-url:

   ajq --backend openai --base-url http://127.0.0.1:8000/v1 --model my-model \
     '.msg =~ "urgent"'
   

Use OpenRouter

1. Export an OpenRouter API key:

   export OPENROUTER_API_KEY="sk-or-..."
   

2. Choose an OpenRouter model id:

   printf '{"msg":"urgent billing issue"}' \
     | ajq --backend openrouter --model openai/gpt-4o-mini '.msg =~ "urgent"'
   

   OpenRouter uses its documented default API root; see the backends reference.

Keep a spending guardrail

Lower the call cap while testing:

ajq --cloud --max-calls 10 '.[] | select(.msg =~ "urgent")'

See Control semantic costs for the full estimate/cap/stats workflow.

Related

• Backends reference — defaults, required settings, and caps.
• Configuration reference — precedence and env-only API keys.