Connect Oh My Pi (OMP) to ApiClo

Before you start

• Create a separate ApiClo API key and check balance and the selected model's current rates.
• Use the client version matching the linked documentation. Keep credentials out of project files.

Steps

1. Connection

   Set APICLO_API_KEY before starting omp. In models.yml, add the apiclo provider using the example below; preserve existing providers.

2. Model and credentials

   Add model IDs from ApiClo's current table. For supported vision models declare input: [text, image]; do not copy context or output limits from a different model.

3. Verification

   Run omp models find apiclo and select your model. A disabled provider is excluded even with valid credentials, so check disabledProviders when it does not appear.

Examples

export APICLO_API_KEY="YOUR_APICLO_KEY"

$env:APICLO_API_KEY="YOUR_APICLO_KEY"

providers:
  apiclo:
    baseUrl: https://apiclo.com/v1
    api: openai-completions
    apiKey: APICLO_API_KEY
    models:
      - id: claude-sonnet-5
        name: Claude Sonnet 5
        input: [text, image]

Check the result

Send one small request and inspect ApiClo Logs for the exact model, outcome and charged usage. Test tool calls and images separately. Cache settings in the client do not prove a hit: check actual read/write token counts.

Troubleshooting

• OMP treats an unresolved apiKey variable name as literal key text. Ensure APICLO_API_KEY is set; otherwise authentication fails even though the YAML is valid.
• For 401, check the active key and credential source; for 404, check the request URL and model ID. Preserve the sanitized error body for support.

Compatibility and billing

ApiClo is an independent gateway. A client integration does not include that client's subscription or guarantee all its features. Compare ordinary input, cache reads, cache writes and output at current model rates; cache hits and savings are workload-dependent.

Sources

• Oh My Pi (OMP)