Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Setting Up AI Authoring

Author with AI drafts a HYPR AgentPass™ policy from a goal you write in plain English. By default, the HYPR built-in author does the drafting: the gateway calls an Anthropic model with an Anthropic API key and a model name that you configure, set once for the whole gateway. Until they are set, the wizard opens but the built-in author cannot draft.

The key belongs to whichever Anthropic account issued it, and the calls made with it are billed to that account. HYPR does not supply a key or run the model.

This page is for whoever holds gateway settings. Using the wizard once it is configured is covered in Authoring a Policy with AI.

note

Configuring the drafting model needs permission to edit gateway settings. Using the wizard needs permission to add policies. One person often holds both, but not necessarily. See Roles and Permissions.

What the Gateway Calls​

The built-in author calls Anthropic's Messages API directly from the gateway. It is not one of your connectors. It does not use a connector's credentials, does not appear in the Request Log as agent traffic, and needs no Anthropic connector to exist. The gateway needs outbound HTTPS access to Anthropic's API endpoint.

Any current Claude model works. Drafting uses plain text completion, with no tool use and no streaming, so the choice of model trades drafting quality against cost.

What the Key Is Used For​

The key on this card is used for:

  • Drafting by the HYPR built-in author, on every route that names the built-in author
  • Policy descriptions, the one-sentence, plain-English description of each policy
  • Suggestion wording, the sentence that states each proposed rule under Suggested
  • Preparing uploaded reference documents, when your default route names the built-in author

A cloud agent that you choose as a policy author never uses this key. It drafts with its own connector's credentials, in its own provider account. You choose the author on the Who drafts your policies card, on the same tab. See Choosing Who Drafts Your Policies.

If every route names one of your own agents, the key is optional. Without it, policy descriptions and suggestion wording use plain forms built from the policy and the evidence.

Configure the Key and Model​

  1. Open Advanced → Gateway Settings, and click the Policy Authoring tab. The Policy authoring (LLM) card is at the top.
  2. Under Anthropic API key, paste a key from your Anthropic console, and click Save. The label beside the field changes from Not configured to Configured.
  3. Under Author model, leave the default or enter the model you want the wizard to use, and click Save. The field's help text names the current default.
The Policy authoring (LLM) card on the Policy Authoring tab of Gateway Settings, with a configured key, the Author model field and the AI policy spend card

The key is write-only. Once saved, it is shown masked and never returned again. Update key replaces it with a new one.

The change takes effect on the next draft. Nothing needs restarting.

What Leaves the Gateway​

When the built-in author drafts, each attempt sends one request to Anthropic. A cloud agent you choose as policy author receives the same content. The request carries:

  • Your goal, exactly as you typed it, plus any clarification you added.
  • The connector's context. On a tool connector, this is the catalog of tools the connector exposes: their names, descriptions and argument schemas. On an inference connector, it is normalized digests of recent conversations on that connector: the models and tools in use and the shape of recent turns, not raw transcripts.
  • A summary of recent traffic on the connector, so the model can name what is actually in use.
  • The attribute reference the model must write against, and the action or phase you pinned.

You can see the exact request before it is sent. On the wizard's Compose step, expand Preview the LLM request before sending. What you see there is what leaves.

The traffic context comes from the request examples the gateway retains. On a new deployment with no recorded traffic, the model drafts from the tool catalog alone, and the wizard's backtest has nothing to replay.

Drafting is rate-limited per user, so one person's experiments cannot exhaust the key.

Watch the Spend​

Below the settings card, AI policy spend shows a running count since the gateway last restarted. Click Refresh to update it.

FigureWhat it counts
Input tokens, Output tokensTokens Anthropic reports for each call made with the key on this card: built-in drafts, policy descriptions, suggestion wording and reference document preparation
Draft requestsEvery draft started in the wizard, whichever author handles it
LLM errorsEvery draft attempt that failed because its author was unavailable, timed out or was misconfigured, whichever author handles it

Tokens used by a cloud agent that you choose as a policy author are not counted here. Read them in that agent's provider console.

The counts restart when the gateway restarts. Use them to spot activity, not to reconcile a bill. Your Anthropic console is the record of what the key has cost.

To see the card, you need permission to view gateway settings and to view policies.

When the Key Is Missing or Wrong​

If no key is configured, or Anthropic rejects the key, a draft on a route that uses the built-in author fails at the drafting step. Routes that name one of your own agents are not affected. It shows Draft failed and the message The LLM provider is unavailable … Check the Settings page for the Anthropic API key configuration. Nothing is saved.

Configure or replace the key, and click Author with AI again. The goal you typed is still in the box.