CONSOLEJOIN US→
Reference

Packages & Versions

AgentOps publishes exactly one package today. If you see a different name anywhere, it is not ours — check it against this page before installing.

Published packages

PackageVersionRegistryWhat it is
@agops-labs/sdk0.2.0npm (public)Guarded fetch + REST + MCP client for the AgentOps guard
bash
npm install @agops-labs/sdk@0.2.0

NOTE

0.2.0 is the latest tag; 0.1.0 is still installable. The package is pre-1.0: minor versions may still change the client surface. Pin the exact version in production.

Version history

  • 0.2.0 — adds createGuardedFetch, a drop-in fetch that handles the x402 handshake, plus the PaymentDeniedError / PaymentFlowError types. Purely additive — 0.1.0 code runs unchanged.
  • 0.1.0 — initial release: REST + MCP clients.

What’s inside @agops-labs/sdk

  • createGuardedFetch — a fetch that pays for 402-gated resources automatically. The recommended path for agents calling paid services.
  • createAgentOpsClient — typed REST client (create/revoke agents, attach trading flows, authorize, read decisions).
  • createAgentOpsMcpClient — JSON-RPC 2.0 MCP client for the same guard (tools/list, tools/call).
  • Full TypeScript types for inputs, results, and decision shapes.

Both clients talk to the same AgentOps server and use the same API keys. Importing one does not pull in the other at runtime.

Package facts

  • License — MIT.
  • Module format — ESM only ("type": "module"). There is no CommonJS build.
  • Runtime — Node.js >=18, or any runtime with a global fetch.
  • Entry points — ./dist/index.js with types at ./dist/index.d.ts; single . export.
  • Dependencies — none at runtime.

Not published by AgentOps

  • mcp-remote — a third-party bridge used in MCP client configs to reach the AgentOps HTTP MCP endpoint. Useful, but not maintained by us.
  • There is no AgentOps CLI, no Python package, and no separate MCP server package. MCP is served by AgentOps itself at /v1/casper-guard/mcp — nothing to install.

Not a package: the GuardRegistry contract

The on-chain anchor lives in the GuardRegistry Odra contract deployed on Casper. You do not install it — AgentOps writes to it on your behalf, and you verify against it. See the on-chain anchor page for how to check a decision hash yourself.

← PreviousEnd-to-End: x402 PaymentNext →Credentials & Keys