PBJ — Pasti Bahagia Jaya

Connect protocols across chains and ship production-ready tools from one workspace.Connect deployed contracts across chains, normalize every interface into one reliable schema, and ship production-ready MCP tools and APIs your agents and applications can use from a single workspace.

Follow on Try Protocol

Overview / Developer WorkspaceProtocols / Jupiter Aggregator

Search⌘ K

DEVELOPER WORKSPACE

Workspace overview

Projects, integrations, traffic health, and recent requests.

PROJECTS12

PROTOCOLS28

GENERATED TOOLS84

HEALTHY REQUESTS99.8%

Request performance

Latency for the latest seven requests.

142 ms avg

Recent integrations

Newest projects and protocols.

DeFi Infrastructure3 protocolsDEV

Stablecoin APIs3 protocolsDEV

Jupiter Aggregatorsolana · mainnetACTIVE

Recent activity

Latest stored protocol requests.

View all logs →

get_balanceJupiter Aggregator20096 ms

get_block_numberUSDC on Ethereum200132 ms

get_contract_codeUSDC on Base200184 ms

get_latest_blockhashJupiter Aggregator422241 ms

J

DEFI INFRASTRUCTURE / SOLANA

Jupiter Aggregator

Live protocol integration with generated MCP tools.

Sync RPCGenerate tools

NETWORKsolana · mainnet

PROGRAM ADDRESSJUP6Lk...v4Z5

INTERFACEAnchor IDL · v6

LAST SYNCEDJust now

MCP tools

Protocol capabilities exposed to agents.

get_balanceRead the native SOL balance for an address.READ

get_latest_blockhashFetch a recent blockhash for transaction construction.READ

get_program_accountInspect an account owned by the protocol.READ

Connect to an agent

MCP-compatible configuration.

● active

"jupiter-mainnet": {
"url": "/api/mcp/jupiter",
"auth": "Bearer pbj_dev_••••"
}

Recent requests

get_balance20096 ms

get_latest_blockhash200132 ms

get_program_account200184 ms

Normalized schema

{
  "chain": "solana",
  "network": "mainnet",
  "protocol": "Jupiter Aggregator",
  "functions": ["getBalance", "getAccountInfo"]
}

Protocols in. Products out.Everything between, handled.

NORMALIZE

BUILT FOR PROTOCOL TEAMS

One clean interface for every chain.

01 / CONNECT

PLATFORM UPTIME

99.5%

Reliable by default.

Consistent protocol access keeps agents and applications moving.

ABOUT — 01

A focused bridge from deployed protocols to agent-ready products.

Start building

PROTOCOL OVERVIEW

One bridge for the entire connected protocol stack.

99.5%UPTIME

84+GENERATED TOOLS

4SUPPORTED CHAINS

Everything your protocol needs.

Connect, normalize, generate, secure, and observe every integration through one consistent protocol layer.

Connect Every Supported Chain

Configure Solana and EVM RPC endpoints once, then reuse them safely across every project.

One Schema Across Protocols

Turn ABIs and IDLs into one deterministic protocol schema your entire stack can understand.

Generate MCP Tools Instantly

NEW

Create agent-ready read operations from verified protocol definitions in a few deliberate steps.

Ship Reliable Typed APIs

Expose the same protocol capabilities through predictable endpoints built for your applications.

Control Every Credential Scope

Issue revocable keys with precise environment, project, and permission boundaries.

Observe Every Protocol Request

LIVE

Inspect status, latency, activity, and failures from one complete request history.

Protocol to production in three moves.

One connected workflow turns deployed protocol interfaces into secure, observable building blocks for applications and agents.

STEP 01

Connect your protocol source

Choose a project, select its network, and connect the contract or Solana program you want PBJ to understand.

STEP 02

Generate one clean interface

PBJ normalizes the ABI or IDL, then produces typed APIs and MCP tools from the same verified schema.

STEP 03

Ship with complete confidence

Create scoped credentials, connect your application or agent, and monitor every request from the dashboard.

PBJ QUICKSTART

TypeScriptquote.ts

import { PBJ } from "@pbj/sdk"; const bridge = new PBJ({apiKey: process.env.PBJ_API_KEY,}); const quote = await bridge.protocol("jupiter").tool("get_quote").run({ amount: 1_000_000 });

RESPONSE200 OK

{"route": "best","outAmount": 143.82,"latency": "82ms"}

One normalized call. Fully scoped, logged, and ready for your product.

Start simple. Scale without limits.

Starter

$0forever

$0 total — no card required

For individual developers exploring protocol integrations and agent workflows.

1 active project
5 protocol connections
25K monthly requests
Community support

Start building

Pro

Scale

Custombuilt for you

Tailored to your annual volume

For organizations that need dedicated capacity, governance, and support.

Custom request volume
Dedicated infrastructure
Team access controls
SLA and onboarding
Direct engineering support

Talk to us

Choose the capacity you need today, then grow without rebuilding your protocol integration stack.

Install once. Build anywhere.

Use PBJ from local development to production agents with one package and one normalized protocol interface.

View on GitHub

DRAG TO EXPLORE

Clear answers. Faster building.

Everything you need to understand how PBJ connects protocols, generates tools, and protects production access.

PBJ connects deployed EVM contracts and Solana programs through the RPC endpoints you configure. Their ABIs and IDLs become one normalized interface for your projects.

No. PBJ sits between your existing deployed protocols and the products that consume them. You keep the contracts and programs you already operate.

PBJ reads the verified protocol schema, identifies available operations, and generates scoped MCP tools that agents can discover and call through your server.

Yes, when explicitly enabled. Write tools remain permission-aware and can be restricted by project, environment, credential, and your approval flow.

Keys are scoped, revocable, and stored separately from the protocol interface. You can issue the smallest permissions required and revoke access without rebuilding an integration.

Yes. PBJ records request status, latency, project, protocol, and operation details so your team can inspect activity and diagnose failures from one place.

Ask ProtocolAI