Gixo for builders

One accepted maximum. One saved operation.

Native generation uses Gixo’s existing engines across eight products and nine workflows. Paid execution requires an enabled native API, a published rate card, an active platform purchase and enough separate platform allowance. Real trial execution uses an enrolled verified account, approved bounded profiles, an evaluation key and a separate allowance for each workflow; its buyer price is $0. Both require explicit acceptance before generation. Creating a key grants no allowance. The free deterministic simulator calls no models.

Enroll and prepare a real trial

Choose “Try real output” in the playground. Sign in, verify your primary email and explicitly start the trial. Status reads create no allowance. Retrying enrollment retains the original window and independent workflow balances. A key alone grants nothing. Create a separate evaluation key under Connect your application and paste it into the trial panel; it stays in memory.

Folio’s setup asks for language and source notes, then saves one personal chapter without a model call. Sequence’s setup requires script-use permission and saves a short graphics-only plan. Review and explicitly confirm that exact saved script before requesting a render quote. Setup never starts generation. Changing setup input cannot overwrite an existing trial draft.

Trial quotes show $0 buyer price and a maximum trial-unit allowance; accept that maximum for this exact request. Expiry or exhaustion does not fall back to paid mode. Production and evaluation references are stored separately; switching modes clears the connected key. Existing saved results remain readable with valid matching read credentials after trial expiry.

Enrollment and setup use your signed-in session with CSRF protection. REST generation uses an evaluation key, the same quote/accept/poll/export routes and language examples, and the selected workflow’s permissions. Real trials do not grant free MCP generation; authenticated MCP generation remains paid.

1. Test the integration first

Use free integration test mode to exercise polling, findings, downloads and errors. Then select real native output in the playground. Enter a matching evaluation or production platform key with the destination workflow’s read and write permissions. The key stays in the page’s memory. Saved request references contain IDs, an input hash and accepted ceilings; they contain no prompt, key or quote token.

Folio needs an existing saved book and chapter. Set sourcingMode: "ReferenceOnly" to draft from your supplied notes without web search. WebAllowed permits web enrichment; omitting the field keeps the existing Auto behavior. A review based only on search excerpts stays unconfirmed. Sequence needs an existing reviewed project, its current revision and its plan fingerprint. Obtain these through the Gixo app before requesting a quote. Sequence’s render uses the reviewed project; it does not invent a new plan from an arbitrary prompt.

Business draft acknowledgement

Before quoting a Business brief, explicitly accept a private draft with unreviewed evidence by setting acknowledgeUnreviewedEvidence: true. The playground provides an unchecked acknowledgement. This approves no evidence item and allows no publishing or delivery; the result remains marked for review. Recommendations and packs do not use this profile.

2. Quote the exact input

POST /api/platform/native/{workflow}/quote with {"input":{…}}. The reply gives token, maximumUnits, maximumPriceMinor, currency, rateCardVersion and expiresUtc. Quoting starts no model call and reserves no generation allowance. Display both ceilings and the currency to the person accepting them. Editing input or changing credentials requires a new quote.

3. Accept once, and save the reference before sending

POST /api/platform/native/{workflow} with {"input":{…},"quoteToken":"…","idempotencyKey":"one UUID for this output"}. Save the exact original input securely in your own system, its idempotency key and the accepted ceilings before submitting. Use a new identity only for a deliberately separate output. The response carries operationId and statusUrl. The operation ID identifies admission; the saved item ID identifies the generated content.

Admission checks access and accepted terms before generation. Do not automatically reprice or accept a larger maximum. HTTP 429 includes Retry-After; wait that long and keep the original identity. A declined or expired quote creates no replacement run.

4. Recover a lost reply

Poll GET /api/platform/native/{workflow}/{operationId}. If the initial reply was lost, retry the original create with the same key, input and idempotency key. After refresh, the playground asks for the exact original input and credential. It may send an empty quote token to recover an existing operation; that token cannot admit a new operation.

admission-pending or output-pending means keep checking the original. A story definition may become readable after its placeholder; this does not authorize a replacement run. recovery-required means the outcome is uncertain and the existing hold is retained; no second generation is dispatched. Keep its reference for support. not-admitted confirms the operation did not start and its allowance was released. A deliberately new request still requires a new quote and acceptance. Missing evidence is never treated as proof that generation did not happen.

5. Inspect and download the saved result

A usable result appears under artifact, with status, review status, findings and export formats. Findings accompany the saved draft. The source receipt includes the saved source ID and version, with outOfDate when freshness can be checked. Do not treat not-reviewed as an approval. Source review compares text with the supplied evidence and reports missing or incomplete coverage. Folio separates clearly labelled proposals and fictional illustrations from empirical claims, while respecting the author’s scope; a reviewed result establishes no tested effectiveness for an authored method. Sequence review covers planned on-screen text, narration script and chart data; it does not visually or aurally inspect the rendered footage, pictures or audio.

GET /api/platform/native/{workflow}/{operationId}/export/{format} requires the platform key. It returns native file bytes or JSON with downloadUrl. Fetch a signed storage ticket separately, without forwarding your platform key. Keep credentials in your backend for production integrations. The browser playground downloads with an authenticated fetch.

6. Convert by saved item ID

Where an existing app conversion is supported, send sourceContentId and expectedSourceVersion in the destination input. The key must read the source workflow and write the destination. Lumen decks and Lumen story (Stanza) have separate workflow permissions within the same product. Their deterministic conversions retain the source link. Lex accepts eligible Business or Arc documents as saved sources; Quill articles are not a Lex handoff. A source changing after quote or preview requires a fresh check; IDs from unrelated stores are not conversion receipts.

For a personal story you own, choose lumen and attach the story’s saved item ID and API content version. This uses the existing deterministic story-to-deck conversion. Its editor revision is checked separately by Gixo; do not substitute it for expectedSourceVersion. The key needs stanza.read and lumen.write, plus lumen.read to retrieve the result. The playground offers only this supported outgoing story destination and requests a fresh maximum and acceptance. Team and shared stories do not use the personal native allowance.

Conversion warnings and source qualifications remain on the saved result. A carried source review is out of date for the converted document until a review covers that document. If source-read access is unavailable, source freshness is unavailable too.

Language examples and paid MCP

The playground’s code panel offers quote, explicit acceptance, polling and export requests for cURL, JavaScript, TypeScript, Python, C#, Java, Go, PHP and Ruby, for every workflow. Quote and acceptance examples follow the request JSON currently shown, including saved source IDs and explicit draft acknowledgements. Input stays in this page’s memory; copying or downloading includes that input. Credentials, quote tokens, idempotency keys and operation IDs remain uppercase placeholders for your application to supply. Invalid JSON clears the payable example until you correct it. These are individual request examples; acceptance requires your application’s explicit price review.

Authenticated native MCP uses the same admission service, scopes, quotes, ceilings and idempotency rules as REST. It needs a production platform key with mcp and workflow permissions and spends the platform allowance. Anonymous tools remain deterministic. Do not expose a key in a model prompt or tool description.

Continue from a saved result

Attach the saved item ID and its content version to a supported destination. This prepares the next request; it does not generate or spend allowance. Review the destination input, request its maximum and explicitly accept it. The API rechecks source read access, destination write access and the saved version, and returns the source receipt and freshness marker.

Campaign: Quill can feed a Prism infographic or Lumen story (Stanza); a saved story can become a Lumen deck through the existing deterministic converter. Sales: an Arc proposal or an independent Business report can feed a Lumen deck. Prism handoffs require kind infographic; an edited chart is left unchanged and must be changed explicitly before attaching a source.

To branch, return to the original source workflow and check its original operation, then attach that result to the other destination. An already accepted destination retains its operation. Check it, or explicitly forget its local reference before preparing a separate output. Every new output needs its own maximum acceptance.

Folio publication conversions use approved workspace/chapter selection in the app. Their typed public handoff adapter is not exposed here; a workspace:chapter ID is not a generic content ID. A Lumen deck can feed Sequence through the app source adapter, but rendering requires a separately saved and explicitly reviewed project, revision and plan fingerprint. The native render API does not accept a deck sourceContentId.