Agent Quickstart

Who this is for

Use this guide if you are:

• evaluating Rynjer for an agent or workflow
• trying to reach a first successful generation quickly
• deciding whether to start from docs, pricing, or a model page

If you are still deciding whether Rynjer fits the task at all, read For Agents first.

The shortest path

1. Check whether the task is a good fit for Nano Banana 2
2. Review pricing if credits matter before integration
3. Create or obtain access credentials
4. Estimate cost with /v1/credits/estimate
5. Send the first request to /v1/generate
6. Poll /v1/generate/{requestId} if the task is still pending

Step 1: pick the right first model

Start with Nano Banana 2 when you need:

• fast prompt-to-image output
• a high-signal evaluation path
• quick builder validation before deeper workflow work
• a practical first landing page with pricing context

Do not treat it as the right answer for every workflow. It is weaker when you need:

• deep multi-step production pipelines
• heavy enterprise evaluation requirements
• strong brand consistency across many outputs

If the task still looks like a fit, continue with the Nano Banana 2 Agent Guide.

Step 2: choose the access path

Rynjer currently supports two practical authentication paths:

Option A: API key → short-lived access token

This is the best default if you are building or testing an autonomous agent flow.

High-level flow:

1. Register an agent identity with POST /api/v1/agents/register
2. Bind the returned registration code to a user account
3. Create an API key with POST /api/v1/agents/keys/create
4. Exchange that API key for an access token with POST /api/v1/agents/auth/token
5. Call /v1/credits/estimate, /v1/generate, and /v1/models/list

Option B: Existing account path

If you already have a working account and only need the app-level agent endpoints, go straight to the Agent API and the current machine-readable docs.

Step 3: estimate before you generate

Use /v1/credits/estimate before the first paid call.

Example:

curl -s https://rynjer.com/v1/credits/estimate \
  -H "Authorization: Bearer $RYNJER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "image",
    "model": "nano-banana-pro",
    "units": {
      "count": 1,
      "resolution": "1K"
    }
  }'

Why this matters:

• confirms the model/product pairing
• exposes the current price_version
• reduces surprises before generation

Step 4: make the first generation call

Minimal example:

curl -s https://rynjer.com/v1/generate \
  -H "Authorization: Bearer $RYNJER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "request_id": "demo-uuid-001",
    "model": "nano-banana-pro",
    "prompt": "Studio product shot of a matte black smart speaker on a neutral background, soft commercial lighting, premium ad look"
  }'

Notes:

• request_id is required
• reusing the same request_id is idempotent and should not double-charge
• product can be omitted if the model already makes it obvious

Step 5: poll for the result

If the first response is still pending, poll:

curl -s https://rynjer.com/v1/generate/demo-uuid-001 \
  -H "Authorization: Bearer $RYNJER_ACCESS_TOKEN"

That is the fastest way to close the loop from first request to usable output.

Token flow shortcut

If you need the autonomous agent path, the shortest machine-first sequence is:

1. POST /api/v1/agents/register
2. bind registration_code
3. POST /api/v1/agents/keys/create
4. POST /api/v1/agents/auth/token
5. call /v1/*

Full curl examples live in Agent API.

Recommended follow-ups

• Need task fit guidance → Nano Banana 2 Agent Guide
• Need endpoint details → Agent API
• Need model-choice logic → Model Routing Guide
• Need product-level context → For Agents