Overview#
A developer building a new widget for the Argus platform needs to understand how the platform's entity enrichment API works, what the standard patterns are for connecting to WebSocket subscriptions, and how to structure the authentication header for a specific endpoint. Instead of searching through documentation pages, she asks the Developer Assistant. It knows the platform's patterns, generates the relevant code snippet, and explains the context, turning a 30-minute documentation search into a two-minute interaction.
Key Features#
- Virtual development assistant with AI-powered code guidance.
- Widget development support with template generation.
- Platform documentation search and contextual help.
- AI routing for domain-specific development queries.
- Code snippet generation for common platform patterns.
- Interactive help centre integration.
- Multi-language support for development assistance.
- Context-aware responses based on current development task.
Use Cases#
Platform developers get AI-assisted guidance for development tasks, asking questions about platform patterns and receiving contextually relevant code examples without navigating the full documentation tree.
Widget builders generate templates and code scaffolding for new dashboard widgets, starting from working examples that follow the platform's widget development conventions rather than building from scratch.
Integration engineers search platform documentation for API usage patterns and integration examples, with the assistant surfacing the most relevant sections based on the specific integration they are working on.
Junior developers troubleshoot development issues with contextual AI support, receiving explanations that account for the specific platform patterns and conventions relevant to their current task.
Integration#
Integrates with widget development, AI provider routing, and help centre documentation for comprehensive developer support.
Open Standards#
- GraphQL (June 2018 specification): The developer assistant's entire API surface is exposed as a GraphQL schema; the assistant provides dedicated guidance, query templates, and code snippets for GraphQL queries, mutations, subscriptions, and fragments.
- OAuth 2.0 (RFC 6749): Authentication guidance explicitly covers OAuth flows, token refresh, and API key management; generated code templates demonstrate Bearer token authorisation headers as defined by OAuth 2.0.
- JSON Web Tokens (RFC 7519): The assistant advises on JWT-based authentication patterns and generates code for token acquisition and verification when developers query the authentication context.
- BCP 47 Language Tags: All supported locales (en-US, en-GB, es-ES, fr-FR, zh-CN, ar-SA and others) are represented using IETF BCP 47 language tag syntax throughout the localisation content model.
- JSON (RFC 8259 / ECMA-404): All API payloads, webhook configurations, translation objects, and code snippet metadata are serialised as JSON; partner tier preferences and onboarding state are stored in JSONB using the same format.
- WebSocket Protocol (RFC 6455): GraphQL subscription support is delivered over WebSocket connections; the assistant surfaces guidance on connecting to and managing WebSocket-based subscriptions as a named assistance context.
- HTTP Semantics (RFC 9110): Generated cURL integration templates and authentication code examples follow HTTP request/response semantics, including the Authorization header field with Bearer credentials.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14