Skip to main content
Registering an agent packages your code with infrastructure, environment config, and a live public endpoint, all in one four-step wizard. To get started, click Register & List in the left-side menu. Test the live endpoint before sending it to the Marketplace.

​
Configure the GMI MaaS endpoint in your image

Before you wrap your agent into an image, read the GMI MaaS connection details from these environment variables. At runtime, GMI injects the API key for the models you select in Step 2, so you never ship a key inside your image.
VariableDescriptionExample
GMI_MAAS_BASE_URLOpenAI-compatible base URL for GMI MaaS.https://api.gmi-serving.com
GMI_MAAS_API_KEYMaaS API key. Injected by GMI at runtime — do not hardcode it.(injected)
GMI_MODELSModel ID your agent calls.deepseek-ai/DeepSeek-V4-Pro
Read these variables in your code rather than hardcoding values, for example: 
import os
from openai import OpenAI

client = OpenAI(
    base_url=f"{os.environ['GMI_MAAS_BASE_URL']}/v1",
    api_key=os.environ["GMI_MAAS_API_KEY"],
)

response = client.chat.completions.create(
    model=os.environ["GMI_MODELS"],
    messages=[{"role": "user", "content": "Hello"}],
)
Leave GMI_MAAS_API_KEY unset in your image — GMI injects it at runtime when MaaS integration is enabled (Step 2). Hardcoding a key is unnecessary and will be overridden.

​
Pick a deployment path

​
GMI CE Deployment

GMI hosts your container on GMI Infrastructure and exposes a public URL. Eligible for the Verified badge when paired with MaaS.

​
Self-hosted + MaaS

You host the agent yourself and call GMI Models-as-a-Service for inference. Lists with the Powered by GMI MaaS badge.

​
Wizard steps

  1. Basic Info
  2. Infrastructure
  3. Env Variables
  4. Review & Register

​
Step 1: Basic Info

Identity for the listing. This is what users see on the catalog card and detail page.
Register an agent, Basic Info
If you’re going with the self-hosted + MaaS path, the Basic Info step looks slightly different:
Register an agent, Basic Info (MaaS path)
Basic Info
  • Add the internal project name

​
Step 2: Infrastructure

Configure compute resources. GMI Infrastructure provisions containers on demand.

​
Docker image source

  • Registry URL. Pull from Docker Hub, GHCR, or any public/private registry.
  • Upload Image. Push a local image directly to GMI’s registry. Useful for one-off builds.

​
Registry URL

  • Format: registry.hub.docker.com/your-org/your-agent:latest
  • Private registries: add credentials in Step 3 as secrets.

​
Compute tier

  • Standard — 2 vCPU · 4 GB RAM · Ephemeral Storage 10 GiB · Data Storage 30 GiB. Additional tiers coming soon.

​
Region

  • Choose from US West, US East, Asia (Singapore), or Europe (Germany).
  • Pick the region closest to your users to minimize latency.
  • Multi-region rollouts require a separate deploy per region.

​
MaaS integration

  • Toggle on to give your agent access to GMI’s 200+ frontier models.
  • GMI injects a MaaS API key into your container at startup, no key management on your end.
  • Select every model your agent may call. Selection is editable later.
  • Required for the Verified badge.

​
Step 3: Env Variables

Runtime configuration injected into your container at startup.

​
Plain values

  • Non-sensitive config: feature flags, base URLs, log levels.
  • Visible in the dashboard and editable anytime.

​
Secrets

  • API keys, third-party credentials, and any sensitive value.
  • Encrypted at rest and redacted from all logs.
  • Write-once: values can be replaced but never read back from the UI.

​
Per-region overrides

  • Override values per region for staged rollouts or region-specific endpoints.
  • Only available when the agent is deployed to more than one region.

​
Step 4: Review & Register

Confirm settings, register, and verify before submitting the listing.

​
Review screen

  • Every setting from the previous steps is summarized on one page.
  • Click any section to jump back and edit.

​
Register

  • Once registered, GMI AgentBox pulls the image and builds the container on demand. Users can then call the endpoint to start or stop the instance — billing runs only for the duration the container is active.
  • The endpoint provided is used for container CRUD.
Test the endpoint
Test the deployed endpoint
  • Hit the URL with a sample request. Confirm latency, output, and error handling.
  • Iterate by re-registering. URLs stay stable across updates.
Next
  • When the endpoint is ready, continue to List an agent to submit it for review.