For AI-native software & SaaS

Develop creative features for your product.

Explore generated scenes in Creator, then use the developer examples below to evaluate text and image features for your application. The examples show individual model outputs, not an automated campaign workflow.

Example workflow

Campaign Builder

The brief · Launch a sculptural cobalt-blue desk lamp with an English headline and a widescreen product image.

Cobalt-blue Luma desk lamp

Nano Banana 2 · 1376 × 768 PNG

Launch headline · Claude Opus 5
Luma: Cobalt-Blue Aluminum, Brilliantly Focused Light

Why Token360

One platform from evaluation to production.

Ship more than one AI feature

Add copy generation and product images through the same platform and credentials. Use the endpoint for each modality from your existing backend.

See the two API requests →

Choose models using your own inputs

Try a representative brief before wiring the feature into your app. Compare the outputs against what your users need, then choose the model for each step.

Try the Playground →

Know what each workflow uses

Use API response metrics and Token360 billing records to understand spend. Tie requests to your app’s customer and feature IDs to calculate unit costs.

See measured usage →
Quickstart

Build the Luma launch in two requests.

Set TOKEN360_API_KEY in your terminal. In production, send both requests from your backend and keep the key there.

Generate the headline
curl --fail-with-body https://api.token360.ai/v1/chat/completions \
  -H "Authorization: Bearer $TOKEN360_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
  "model": "claude-opus-5",
  "messages": [
    {
      "role": "user",
      "content": "Write one short English launch headline for a fictional desk lamp named Luma, made from cobalt-blue anodized aluminum. Return only the headline."
    }
  ]
}'

Returned headline: Luma: Cobalt-Blue Aluminum, Brilliantly Focused Light

Generate the product image
curl --fail-with-body https://api.token360.ai/v1/images/generations \
  -H "Authorization: Bearer $TOKEN360_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
  "model": "nano-banana-2",
  "n": 1,
  "aspect_ratio": "16:9",
  "prompt": "Editorial launch photograph of Luma, a fictional sculptural cobalt-blue anodized aluminum desk lamp on a pale limestone plinth. Warm light pools under its conical shade, late-afternoon shadows across an ivory wall, strong blue silhouette, wide 16:9 composition. No text or logos."
}'

Returned one product image. The preview above displays the downloaded 1376 × 768 PNG.

See what these requests used →

Usage & cost

Track what each campaign uses.

Claude Opus 5
54 input · 26 output · 80 total tokens
Nano Banana 2
1 generated image

These figures come from the Luma API responses. For campaign cost, record a campaign ID alongside each request in your app and reconcile the two charges against Token360 billing records.

Apply this pattern to your product →

SaaS use cases

Give users a finished starting point.

Illustrative example

Customer
Can I change my delivery address?

Reply draft
Send us your order number and we’ll check whether the address can still be updated.

In-app Assistant

Give support teams an editable reply based on the selected conversation.

Illustrative invoice extraction
Invoice
INV-1042
Total
$248.00
Due date
Needs review

Document Workflow

Extract invoice fields and flag ambiguous values for review.

Production integration

Turn the demo into a product feature.

When a customer submits a campaign brief, create a campaign record in your backend. Save the headline and image against that record so the customer can review them together and regenerate either one separately.

  1. Validate and save

    Check that the headline and image are usable. Store them under the campaign ID.

  2. Recover incomplete drafts

    Keep successful outputs. After a timeout, check the original request before retrying.

  3. Review and publish

    Let customers edit and approve the copy and image before exporting.

See what to track after launch →

Operating your feature

Measure cost and reliability per campaign.

At request time
Log the campaign ID, customer ID, model, request ID when available, outcome, and elapsed time.
After each response
Record the token counts or image count reported by the API. Track failed steps and retries separately.
When reviewing spend
Reconcile charges with Token360 billing records. Group by customer, feature, or campaign and include any billed retries.

For Luma, the two successful responses reported 80 text tokens and one generated image. Use billed charges to calculate campaign cost. For reliability, track how often both steps finish and how long customers wait for the complete draft.

Read the integration FAQ →

Choose how to evaluate Token360.

Self-serve

Run your first workflow.

Get an API key, then run the two Luma requests from your terminal.

Terminal · Luma quickstart
POST /v1/chat/completions

Luma: Cobalt-Blue Aluminum, Brilliantly Focused Light

For teams

Plan your production rollout.

Discuss capacity, access controls, and billing with the Token360 team.

What to bring

0 of 3 ready

Before you integrate

Which endpoints does the example use?

Use /v1/chat/completions for the headline and /v1/images/generations for the image.

Where should I store my API key?

Store it in your backend environment or secret manager. Your browser calls your own backend.

How do I track cost per customer?

Associate each request with a customer ID in your app, then reconcile its billed charge before aggregating by customer or feature.

What if only one step succeeds?

Save the successful output and show the status of the remaining step. Let the customer retry just that step when it is safe to do so.

How should I test a model change?

Run a fixed set of representative briefs through both models. Review output quality, latency, and billed cost before changing the model for customers.

Build your first AI feature with Token360.