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

@mtc-247ia/bedrock-proxy

v1.0.0

Published

AWS Bedrock Runtime SDK wrapper that automatically tracks API costs to MyTokenCost

Readme

@mtc-247ia/bedrock-proxy

SDK proxy para AWS Bedrock que automaticamente rastreia custos e registra no MyTokenCost.

Bedrock não usa uma chave única — autentica via credenciais AWS (Access Key + Secret Key + Região, SigV4). O construtor pede esses 3 campos em vez de apiKey.

📦 Instalação

npm install @mtc-247ia/bedrock-proxy

🚀 Uso

import { CountedBedrockRuntime, ConverseCommand } from "@mtc-247ia/bedrock-proxy";

const client = new CountedBedrockRuntime({
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  region: "us-east-1",
  token: process.env.MYTOKENCOST_TOKEN,
  projectId: "meu-projeto",
  apiId: "minha-api",
  backendUrl: "https://mytokencost.up.railway.app",
});

// Custos rastreados automaticamente ✨
const response = await client.send(new ConverseCommand({
  modelId: "anthropic.claude-sonnet-5",
  messages: [{ role: "user", content: [{ text: "Olá" }] }],
}));

⚙️ Opções

const client = new CountedBedrockRuntime({
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,     // ✅ Obrigatório
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY, // ✅ Obrigatório
  region: "us-east-1",                            // ✅ Obrigatório
  sessionToken: process.env.AWS_SESSION_TOKEN,     // Opcional (credenciais temporárias/STS)
  token: process.env.MYTOKENCOST_TOKEN,            // ✅ Obrigatório
  projectId: "meu-projeto",                        // ✅ Obrigatório
  apiId: "minha-api",                              // Opcional (default: "bedrock")
  backendUrl: "https://mytokencost.up.railway.app", // Opcional
  debug: true,                                     // Opcional (logs detalhados)
});

⚠️ Limitação

O rastreamento de custo só funciona para chamadas via ConverseCommand (API unificada do Bedrock, com usage padronizado entre modelos). Chamadas via InvokeModelCommand não são interceptadas, pois o formato de resposta varia por provedor de modelo.

💰 Preços Suportados

| Modelo | Input (por 1M tokens) | Output (por 1M tokens) | |--------|-------|--------| | anthropic.claude-opus-4-8 | $5.00 | $25.00 | | anthropic.claude-sonnet-5 | $3.00 | $15.00 | | anthropic.claude-haiku-4-5 | $1.00 | $5.00 |

📄 Licença

ISC