Appearance
Capture AI prompts and responses
These connections bring in what people send to AI models and what comes back, not just the cost. They hold far more sensitive data than the spend connections, so get your security and privacy leads' agreement before you switch them on.
You need access to connect AI providers. Ask your Flowstate admin. For spend only, see Connect your AI providers.
Choose the connection
| Open this in Flowstate | For |
|---|---|
| Anthropic Compliance API | Claude content, collected with a key you provide |
| OpenAI Logs API | OpenAI content, for your whole organisation or one project |
| Amazon Bedrock — content logs | Bedrock content your AWS account sends to Flowstate |
| Vertex AI — content logs | Vertex AI content your Google Cloud project sends to Flowstate |
Enterprise plans
Without an Enterprise plan with the provider, you get metadata only, not full prompts and responses.
Connect Anthropic or OpenAI
- Go to Settings → Integrations, select Browse catalog and open Anthropic Compliance API or OpenAI Logs API.
- Select Connect, then follow the steps on the page to create a key at the provider.
- Paste the API key.
- For OpenAI, choose the Scope (Organisation or Project) and enter the Scope ID, which starts
org_orproj_. - Select Verify and connect.
Connect Amazon Bedrock or Vertex AI
- Go to Settings → Integrations, select Browse catalog and open Amazon Bedrock — content logs or Vertex AI — content logs.
- Select Connect and finish the connection. A Webhook endpoint panel appears, with a Webhook URL and a token.
- Select Reveal token, then Copy.
- Give the URL and token to your technical team to set up sending. See For your technical team.
Check it's working
The connection is listed under Connected keys. Content starts to appear in Flowstate's AI governance screens once the provider sends it. See AI in Flowstate.
If something's not right
Only metadata arrives, not full prompts and responses. Your plan with the provider doesn't include full content.
Nothing arrives from Bedrock or Vertex AI. Check the sending set-up uses the exact Webhook URL and token from the panel.
For your technical team
- Amazon Bedrock: switch on model invocation logging in Bedrock and send the logs through an Amazon Data Firehose delivery stream to the Webhook URL. Set the token as the
X-Amz-Firehose-Access-Keyheader on the delivery stream. - Vertex AI: create a Pub/Sub push subscription for your request and response logs, pointed at the Webhook URL with the token on the query string (
?token=).