GRIDNEXA DEVELOPER DOCS

GridNexa developer documentation

Understand the model capabilities available on GridNexa, then connect an existing application to unified invocation, task, and artifact APIs.

View platform overview Open Developer Console

Choose a task

Choose an integration path

Call GridNexa model capabilities directly or publish a developer application. Application workers can also call platform models while handling requests.

CALL AI CAPABILITIES

Call GridNexa models

Use a developer API key with /v1/invoke. GridNexa handles capability validation, model selection, routing, billing, and result delivery.

Make the first call

INTEGRATE AN EXISTING APP

Adapt and connect an application

Keep the existing business API and add a server-side GridNexa provider, input assets, asynchronous tasks, and generated artifacts.

View the integration steps

Invocation endpoints

Two invocation endpoints

One endpoint provides platform model capabilities; the other invokes a published application. Applications can call platform models while processing a request.

POST /v1/invoke

A developer application calls a platform model

capability is required and model is optional. The platform selects an execution backend from the market policy and published model binding.

POST /v1/apps/:id/invocations

A user or experience invokes a published app

The platform resolves the same operation to either a Load Balancer HTTP worker or a Queue handler in the current release.

Core guides

Continue by task

CONCEPTPlatform overviewHow platform capabilities, developer applications, and the Marketplace fit together.CAPABILITYExplore model capabilitiesReview the inputs, execution modes, and outputs for text, image, and video tasks.10 MINComplete your first model callCreate a key, send a request, and verify 200 and 202 responses.INTEGRATIONIntegrate an existing applicationKeep your business API and add a server-side GridNexa provider, task polling, and artifact handling.APP APIIntegrate Application InvocationCall a published application through a stable operation.RUNTIMEChoose External, LB, or QueueChoose a runtime based on protocol, duration, and scaling behavior.MARKETPLACEComplete the five-step publishing flowFrom draft and runtime through experience frontends to review and release.

Found a documentation issue?

Choose an issue type, add details, and submit your feedback.