Docs
Checking Raims account
All agents
Anomaly

OpenCode + Raims

A terminal agent with a choice of AI providers for implementing your Raims integration.

Terminal
Official documentationDocumentation for agentsAPI reference

Quick start

  1. Prepare the agent

    Choose the installation for your system in the official OpenCode guide. Configure your AI provider using its documented setup flow. That provider's credential is separate from your Raims API key.

  2. Open your project

    Open a terminal in your application folder and start the agent:

    Shell
    opencode

  3. Add the documentation

    Ask the agent to read Raims' documentation index and open the relevant guides. llms-full.txt provides the consolidated content. Start with authentication and charges.

  4. Try a prompt

    Read https://docs.raims.com/llms.txt and the authentication and charges guides.
Inspect this application's backend and propose a plan to retrieve an existing
Sandbox charge with GET /v1/charges/{id}. Prepare an example using protected
server configuration for the key. Do not send requests or use real credentials.
Show the sources and the files you would change before editing.

Project context

Add the content below to AGENTS.md at your project root. OpenCode uses this file for repository instructions. To generate an initial structure, the /init command analyzes the project; review the resulting file.

Markdown
# Raims integration

- Read https://docs.raims.com/llms.txt before choosing endpoints and fields.
- Use https://docs.raims.com/llms-full.txt for the consolidated documentation.
- API base URL: https://api.raims.com.
- In Raims product installation examples, select the latest stable version
  through the package manager (`latest` where supported).
- Prepare examples for Sandbox, with Bearer authentication in the backend.
- Keep the key in protected server configuration. Never put secrets in code,
  prompts, logs, or browser applications.
- Explain the plan and request authorization before sending API requests.

Verify the setup

Ask the agent to identify the guides it read, the API base URL, and the place in your backend where the key will be loaded. It should prepare the plan and example without asking you to paste a real credential.

Reading the documentation does not authenticate the application. Requests use a Raims API key for the intended company and environment.

Common issues

Official sources

GitHub Copilot + Raims

An editor assistant for planning and writing Raims integration code.

Vibe + Raims

Mistral's terminal agent for preparing backend code that connects to Raims.