AWS Amazon Bedrock Runtime API

Name: Amazon Bedrock Runtime API
Brand: Amazon Bedrock Runtime API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage ModelsapiKey5 Endpoints

Install Jentic One Beta

Connect the Amazon Bedrock Runtime API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Bedrock Runtime API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon Bedrock Runtime API.

Invoke any Amazon Bedrock-hosted foundation model with a model-specific JSON body via InvokeModel

Stream tokens incrementally with InvokeModelWithResponseStream for chat UIs and progressive output

Use the unified Converse API to run multi-turn chat across Anthropic, Meta, Mistral, Cohere, and Amazon models without rewriting the request body

GET STARTED

Start building with Amazon Bedrock Runtime API

Explore with Jentic

View OpenAPI Document

For Agents

Invoke Amazon Bedrock foundation models for text generation, chat, and tool-use, with streaming and a unified Converse interface across providers, plus Guardrails for safety.

Use for: I need to generate a chat completion from Claude 3 Sonnet on Bedrock, Stream a long response from a Bedrock-hosted model, Use the Bedrock Converse API across multiple model providers, Apply a Guardrail to user input before sending it to the model

Not supported: Does not train or fine-tune models, manage agents and knowledge bases, or list available models. Use for foundation model inference and Guardrail application only.

Use Cases

Patterns agents use Amazon Bedrock Runtime API for, with concrete tasks.

★ Cross-Provider Chat with Converse

Build a chat product that can swap between Claude, Llama, Mistral, and Amazon Nova without rewriting the request body for each provider. The Converse API normalises messages, system prompts, and tool definitions into one schema; the runtime handles each provider's idiosyncratic format internally. Switching providers becomes a model-id change rather than a code change.

Call Converse on modelId=anthropic.claude-3-5-sonnet-20241022-v2:0 with messages=[{role: 'user', content: [{text: 'Summarise: ...'}]}] and inferenceConfig={maxTokens: 1024, temperature: 0.2}.

Streaming Chat UI

Power a chat interface where tokens render as the model produces them rather than waiting for the full response. ConverseStream emits messageStart, contentBlockDelta, and messageStop events that the front end consumes via SSE or WebSocket. Combined with low-latency models like Claude Haiku or Nova Micro, this delivers sub-second time-to-first-token for end users.

Call ConverseStream on modelId=anthropic.claude-3-haiku-20240307-v1:0 with the user's message, forwarding each contentBlockDelta event to the connected browser over WebSocket.

Guardrail-Filtered Customer Chatbot

Wrap a customer-facing chatbot with Bedrock Guardrails so the model never returns disallowed content, leaks PII, or strays off the policy-defined topic list. ApplyGuardrail evaluates input text against the configured Guardrail and returns an action (NONE, GUARDRAIL_INTERVENED) plus the redacted output. Combine with Converse so model calls already inherit Guardrail enforcement.

Call ApplyGuardrail with guardrailIdentifier=gr-7abc, guardrailVersion=DRAFT, source=INPUT, and content=[{text: {text: 'user message ...', qualifiers: ['guard_content']}}].

Agent Tool-Use with Claude on Bedrock

Let an AI agent use tools, such as searching a database, calling a payment API, or posting to a Slack channel, through Claude on Bedrock with Anthropic's structured tool-use schema. The agent sends tool definitions in the Converse request, Claude returns toolUse content blocks, the agent executes them via Jentic, and feeds toolResult content blocks back. Jentic handles credential isolation for both the Bedrock call and the downstream tool calls.

Call Converse on modelId=anthropic.claude-3-5-sonnet-20241022-v2:0 with toolConfig.tools=[<schemas loaded from Jentic>] and the user's request, then execute each toolUse content block via Jentic and pass the toolResult back in the next Converse call.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for amazon bedrock runtime api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/model/{modelId}/invoke

Invoke a foundation model with a provider-native body

POST

/model/{modelId}/invoke-with-response-stream

Invoke a model with streaming response

POST

/model/{modelId}/converse

Run a unified Converse multi-turn chat call

POST

/model/{modelId}/converse-stream

Run a streaming Converse call

POST

/guardrail/{guardrailIdentifier}/version/{guardrailVersion}/apply

Apply a Guardrail to text input or output

POST

/model/{modelId}/invoke

Invoke a foundation model with a provider-native body

POST

/model/{modelId}/invoke-with-response-stream

Invoke a model with streaming response

POST

/model/{modelId}/converse

Run a unified Converse multi-turn chat call

POST

/model/{modelId}/converse-stream

Run a streaming Converse call

POST

/guardrail/{guardrailIdentifier}/version/{guardrailVersion}/apply

Apply a Guardrail to text input or output

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AWS access key ID and secret access key are stored once, encrypted, by your own Jentic One instance, and the Signature Version 4 signature is computed at execution time. The raw keys never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a chat response with a foundation model' or 'stream model output', and Jentic returns the matching Bedrock Runtime operation with its input schema so the agent calls the right endpoint without crawling the AWS reference.

Time to first call

FAQs

Specific to using Amazon Bedrock Runtime API through Jentic.

Why is there no official OpenAPI spec for Amazon Bedrock Runtime API?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Bedrock Runtime API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Amazon Bedrock Runtime API use?

All requests are signed with AWS Signature Version 4 using an AWS access key ID and secret access key. Through Jentic, the credentials live encrypted in the vault and Jentic computes the signature server-side, so the agent only ever holds a scoped Jentic credential reference.

Which models can I invoke through this API?

Any model your account has access to in Amazon Bedrock, including Anthropic Claude, Meta Llama, Mistral, Cohere Command, AI21 Jurassic, Stability SDXL, and Amazon Titan and Nova families, identified by its modelId (for example anthropic.claude-3-5-sonnet-20241022-v2:0). Access must be enabled per model in the Bedrock console first.

How do I stream tokens from a Bedrock model through Jentic?

Search Jentic for 'stream a chat completion from Bedrock', load the ConverseStream schema, and execute it. The operation maps to POST /model/{modelId}/converse-stream and Jentic forwards the AWS event stream so the agent receives messageStart, contentBlockDelta, and messageStop events as they arrive.

What are the rate limits for the Amazon Bedrock Runtime API?

Bedrock applies per-model and per-account quotas measured in requests per minute and tokens per minute (for input and output separately). Limits vary by model and region; on-demand and provisioned throughput modes have different ceilings, and ThrottlingException is returned when a quota is exceeded.

Is Amazon Bedrock free to use?

Bedrock charges per token for on-demand inference, with separate input and output token rates per model, plus optional Provisioned Throughput pricing for guaranteed capacity. There is no monthly subscription; you pay only for the tokens consumed plus any Guardrails policy units you apply.

Can I limit what my agent is allowed to do with the AWS Bedrock Runtime API?

Yes. Because you run Jentic One yourself, your own rules decide which of the five Bedrock Runtime operations your agent may call, so you can allow Converse and InvokeModel while withholding ApplyGuardrail. Since the model and guardrail identifiers sit in the request path (/model/{modelId}/... and /guardrail/{guardrailIdentifier}/...), a rule can also pin the agent to specific model IDs or a specific guardrail. The AWS access key stays with your instance and the agent only ever holds a scoped credential reference.

AWS Amazon Bedrock Runtime API

Connect the Amazon Bedrock Runtime API to your agent

Capabilities

Start building with Amazon Bedrock Runtime API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs