AI Provider for Ask Sage

[!WARNING] This is a prototype. It is not production software and is not affiliated with or endorsed by Ask Sage. Every request path has been exercised against mocked HTTP responses only — nothing has been validated against a live Ask Sage tenant. Response shapes for the native /server/query endpoint (notably token usage) are inferred from public documentation and may be wrong. Review, test against a real tenant, and confirm trademark usage with Ask Sage before deploying or distributing.

Ask Sage provider for the WordPress AI Client. Lets regulated WordPress sites route AI requests through their own Ask Sage account (FedRAMP High / IL-authorized), with dataset grounding, personas and citations.

Structured to match the official provider plugins and Fueled's Ollama provider.

Install

composer require wpvip/ai-provider-for-ask-sage

Or drop the directory into wp-content/plugins/ and activate — a fallback PSR-4 autoloader is included, so composer install is optional.

// wp-config.php
define( 'ASK_SAGE_BASE_URL', 'https://api.<your-tenant>.ai' ); // GovCloud / IL endpoint
define( 'ASK_SAGE_API_KEY', getenv( 'ASK_SAGE_API_KEY' ) );    // or use Settings > Connectors

Usage

No Ask Sage-specific code is required:

use WordPress\AiClient\AiClient;

$text = AiClient::prompt( 'Summarize the agency travel policy.' )->generateText();

With grounding:

use WordPress\AiClient\Providers\Models\DTO\ModelConfig;

$config = new ModelConfig();
$config->setSystemInstruction( 'You are a policy assistant.' );
$config->setCustomOptions( array(
    'dataset' => array( 'agency_policy_docs' ),
    'persona' => 7,
    'live'    => 0,
) );

$result = AiClient::generateTextResult( 'Is FedRAMP High sufficient?', $config );
$result->toText();
$result->getAdditionalData()['references'] ?? array();

Enforce a mandated corpus site-wide:

add_filter( 'ai_provider_for_ask_sage_query_params', function ( $params ) {
    $params['dataset'] = array( 'agency_policy_docs' );
    $params['live']    = 0;
    return $params;
} );

Architecture

Two surfaces, routed per request

Ask Sage exposes two APIs with complementary strengths, so the provider uses both:

A request is routed to the native surface when any grounding option is set, and to the OpenAI-compatible surface otherwise. Force one with the asksage.endpoint custom option (native or openai).

When a grounded request also sets an OpenAI-only option, grounding wins and a debug notice is raised under WP_DEBUG rather than failing silently.

Ask Sage authenticates with an x-access-tokens header rather than Authorization: Bearer, so a custom RequestAuthenticationInterface implementation is supplied. Requests still flow through the SDK's HTTP transporter.

Option support

Advertised (honored by /server/query): inputModalities, outputModalities, systemInstruction, temperature, customOptions.

Deliberately not advertised: maxTokens, topP, topK, stopSequences, presencePenalty, frequencyPenalty, logprobs, functionDeclarations, webSearch, and output file/schema options. Callers that set these correctly fall through to another provider.

Not implemented on the native endpoint: streaming, and function calling (/server/query accepts a tools array but its format varies by model).

License

GPL-2.0-or-later