npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@onioneko/kiki-llm-bedrock

v0.1.3

Published

AWS Bedrock LLM provider middleware for @onioneko/kiki-core

Downloads

314

Readme

@onioneko/kiki-llm-bedrock

Kiki · Middleware framework for LLM agents

npm install @onioneko/kiki-llm-bedrock

AWS Bedrock LLM provider as middleware. Calls the Bedrock Converse API and pushes the assistant response onto ctx.messages, then calls next() to allow response-processing middleware downstream. Works with any Bedrock-hosted model (Claude, Llama, Mistral, etc.).

Usage

import { compose } from "@onioneko/kiki-core";
import { createBedrockMiddleware } from "@onioneko/kiki-llm-bedrock";

const chain = compose([
  createBedrockMiddleware({ model: "anthropic.claude-sonnet-4-6" }),
]);

const ctx = {
  messages: [{ role: "user", content: "What is 2 + 2?" }],
  system: "Be concise.",
};
await chain(ctx);
// ctx.messages[1] is the assistant response

Configuration

model is required. Other fields are optional with sensible defaults. Authentication uses the standard AWS credential chain (env vars, IAM role, SSO, etc.).

createBedrockMiddleware({
  model: "anthropic.claude-sonnet-4-6", // required
  region: "us-east-1",     // or AWS_REGION env var
  maxTokens: 16384,        // default: 16384
  client: bedrockClient,   // optional: injected BedrockRuntimeClient (for testing)
});

Behavior

  • Non-terminal — calls next() after pushing the response, allowing response-processing middleware to be composed after the LLM.
  • Converse API — uses the unified ConverseCommand, not the low-level InvokeModelCommand. Model-agnostic.
  • Multi-modal — handles both string and ContentBlock[] message content. Images are sent as bytes (base64-decoded).
  • No URL images — Bedrock Converse only supports bytes and S3 locations, not direct URLs. URL-type images are skipped.
  • AWS credentials — uses the standard AWS credential chain. No API key config needed.
  • Config precedence — explicit config > defaults.

Exports

  • createBedrockMiddleware(config) — Factory function returning a Middleware
  • BedrockConfig — Configuration type
  • Re-exports from @onioneko/kiki-types: Message, ConversationContext, ContentBlock, TextBlock, ImageBlock