Requests, results and account history
REST requests use theapi-token header to identify your StealthGPT account. Async status lookup checks that the run belongs to that account. The API dashboard provides account-scoped history with request text, returned content and usage information.
Keep your own copy of completed results and run IDs. Your publishing system should retain the reviewed version of a document and its approval record. The humanization review recipe demonstrates this handoff without publishing directly to a CMS.
See async runs, Stealth Agent and MCP billing for each workflow’s response fields and account behavior.
Processing follows your chosen workflow
StealthGPT processes request content using hosted inference and supporting services. Current implementation paths include:
The route depends on the model, requested features and fallback behavior. Stealth Agent can add research, fact checking and image generation to the workflow. Use the model guide and Stealth Agent controls to choose the capabilities you need. For a processor inventory or a specific processing-region requirement, include your intended workflow in a support request.
Callbacks send results to your endpoint
ProvidingwebhookUrl opts an async run into a terminal callback. That endpoint receives the completed result and billing fields, or the terminal error payload. Choose an endpoint under your control and apply your own access, logging and retention rules there.
Set webhookSecret to receive an HMAC-SHA256 signature. Verify the timestamp and raw request body, deduplicate by run ID, and retain polling as a reconciliation path. The webhook reference documents signing and delivery behavior; the review recipe includes a receiver example.