> ## Documentation Index
> Fetch the complete documentation index at: https://apione.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect RikkaHub to APIONE

> Add APIONE to your Android chat client.

## Add an OpenAI-compatible provider

In RikkaHub settings, add a provider named APIONE and choose **OpenAI Compatible**.

| Field | Value |
| - | - |
| API Key | Your APIONE key |
| Base URL | [https://api.apione.ai/v1](https://api.apione.ai/v1) |
| Separate chat path, if required | /chat/completions |

The combined URL should be [https://api.apione.ai/v1/chat/completions](https://api.apione.ai/v1/chat/completions), with /v1 appearing once.

## Add a model and chat

Fetch the model list, or manually add an actual APIONE model ID. Select it in the assistant or conversation settings and send a test question.

Images, browsing, tools, and reasoning require support from both the client and model. Verify plain text first.

## Use the Gemini protocol

For native Google/Gemini access, add the corresponding provider type with [https://api.apione.ai/v1beta](https://api.apione.ai/v1beta), your APIONE key, and a Gemini-compatible model ID. Use the standard Gemini API mode, not Google Cloud Vertex credentials.

If the client configures API version separately, use the root address and v1beta, ensuring the version appears once in the final path.

## Troubleshoot

For empty model lists, check key permissions. If the assistant uses an old provider, update its model binding. Check image support when image requests fail. For unreliable background connectivity, inspect Android network and battery restrictions.

***

[Integration directory](https://apione.ai/docs/en/guides/clients.md) · [Choose a model](https://apione.ai/docs/en/models/catalog.md) · [Troubleshooting](https://apione.ai/docs/en/support/errors.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.