GlossaryProductsIntermediate

JSON-RPC

Also written: JSONRPC

A protocol for remote procedure calls using JSON to format messages, enabling programs to interact across networks.

In plain terms

JSON-RPC is a way for different computer programs to communicate with each other, even if they are running on different machines.

Think of it like ordering food from a restaurant. You send a request (your order) in a specific format (JSON) to the kitchen (another program). The kitchen processes your order and sends back a response (your food). JSON-RPC standardizes how these requests and responses are sent and received, making it easier for programs to work together.

For example, a web application might use JSON-RPC to ask a separate AI model service to generate text or analyze an image.

The expert version

JSON-RPC is a lightweight remote procedure call (RPC) protocol. It uses JSON as its message format, defining methods to be called and parameters to be passed. A client sends a request object to a server, which then executes the specified method and returns a response object.

It supports both notification calls (where the client does not expect a response) and request calls. Its simplicity and the widespread adoption of JSON make it a common choice for inter-process communication, especially in web services and distributed systems.

Why it matters now

Frontier AI labs are building complex systems that need to communicate between different services. Protocols like JSON-RPC allow these services, whether they are AI models or other backend components, to interact efficiently. This is crucial for creating sophisticated AI applications that can perform a wide range of tasks.

Where it shows up 2 items, newest first
How each company uses it
Google Gemini
Google Cloud API Gateway can expose REST APIs, which can then be accessed by AI agents, potentially using JSON-RPC for communication.
OpenAI ChatGPT
OpenAI's App Server standardizes access to its coding agent across multiple interfaces, suggesting a need for structured communication protocols like JSON-RPC.
Related terms

APIgRPCRESTWebhooksMicroservicesRemote Procedure Call

Often confused with
REST
REST is an architectural style that uses HTTP methods (GET, POST, etc.) an
gRPC
gRPC is another RPC framework, but it uses Protocol Buffers for serializat
WebSockets
WebSockets provide a persistent, full-duplex communication channel b
Origin

JSON-RPC was first specified in 2005 by Tom MacTaggart. It aims to provide a simple, transport-agnostic way to invoke methods remotely using JSON. Source ↗

Try this about 5 minutes

You can explore JSON-RPC by using tools like Postman or Insomnia to send requests to a public JSON-RPC API. Many blockchain nodes expose JSON-RPC interfaces that you can query to get information about the network. Look for documentation for a public API that lists its JSON-RPC endpoints and methods.

Try it: Playbook entries that use thisPlaybook →

The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.

Questions people ask

Is JSON-RPC secure?
JSON-RPC itself does not define security mechanisms. Security is typically handled at the transport layer (e.g., using HTTPS) or through application-level authentication and authorization.
What is the difference between JSON-RPC and REST?
REST is resource-oriented and uses standard HTTP methods, while JSON-RPC is procedure-oriented, focusing on calling specific functions or methods on a remote server.

First seen on Subvolts Feb 4, 2026. Updated Sep 30, 2026. Written by an AI model from the items above and reviewed against them weekly; report an error.