Skip to content

JSON-RPC

A lightweight transport-independent remote-procedure-call protocol encoding requests, responses, errors, identifiers, notifications and batches as JSON objects.

Version
v1 · 2026-09-08 · History
Domain-specific #
5158
Origin domain
distributed systems
Subdomain
application protocols

Core Idea

JSON-RPC specifies how a peer invokes named remote methods and correlates JSON-encoded responses without defining the transport, authentication or application methods themselves.[n1] A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of distributed systems. It is minimal JSON wire semantics for RPC independent of HTTP or another transport. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

Structural Signature

  • Carrier: a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport
  • Inputs or antecedent state: the exact distributed systems carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate JSON-RPC
  • Constitutive operation: A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response.
  • Invariant: messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests
  • Recognition test: type the carrier, state every parameter and convention in the definition, test that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
  • Output or consequence: recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
  • Failure boundary: the carrier is mistyped, the condition that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not

  • It is not the whole field of distributed systems. The field contains many questions and methods that do not instantiate JSON-RPC.
  • It is not its most familiar example. A client sends a version 2.0 request with method 'subtract', parameters and id 1 and receives a result object carrying id 1. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
  • It is not the neighboring catalog concept REST. REST organizes resource representations through uniform interface semantics, commonly HTTP; JSON-RPC exposes named remote procedures and can run over many transports.
  • It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of JSON-RPC must control the decision
  • It is not an unrestricted metaphor for any process that seems similar. Outside distributed systems, the vocabulary and validity conditions do not transfer literally.

Scope of Application

JSON-RPC belongs to distributed systems and is useful where the analyst can specify a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport, then evaluate messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests. The scope is broad within that domain but bounded by the need for messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.[n2]

  • Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
  • Construction or evolution. Track how the exact distributed systems carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate JSON-RPC are converted, constrained, or organized by A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response..
  • Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
  • Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of JSON-RPC must control the decision and state which convention or theorem controls the decision.
  • Downstream reasoning. Use the established identity to support recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity

The abstraction clarifies a crowded vocabulary by making messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name JSON-RPC can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact distributed systems carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate JSON-RPC, the structure counts as JSON-RPC exactly when messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to JSON-RPC. JSON-RPC compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of JSON-RPC. Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport. Reject examples whose alleged carrier belongs to a different problem.
  2. Lock the constitutive rule. Express messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
  3. Derive consequences. From messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests, infer recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
  4. Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of JSON-RPC must control the decision and an object that resembles JSON-RPC in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
  5. Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer

Knowledge transfers strongly among subfields of distributed systems because they reuse a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport, A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response., and type the carrier, state every parameter and convention in the definition, test that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from A client sends a version 2.0 request with method 'subtract', parameters and id 1 and receives a result object carrying id 1. to An API supplies separate authentication, authorization, transport reliability and method schemas because JSON-RPC does not provide them..[1]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of JSON-RPC, preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples

Canonical

A client sends a version 2.0 request with method 'subtract', parameters and id 1 and receives a result object carrying id 1. The example exposes the carrier and directly tests that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport; the operative rule is A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response.; the invariant is messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests; and the result supports recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.[n1] Changing incidental notation or scale leaves the structure intact, while removing messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests destroys the classification.

Mapped back: a client and server, JSON messages, method names and parameters, request identifiers, results or error objects, notifications, batches, and an underlying transport → A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response. → messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests → recognizing and comparing instances of JSON-RPC, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice

An API supplies separate authentication, authorization, transport reliability and method schemas because JSON-RPC does not provide them. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that messages satisfy the selected JSON-RPC version's object shapes and response identifiers correlate exactly with nonnotification requests fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.[n2] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions

  • T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
  • T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
  • T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
  • T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
  • T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
  • T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of JSON-RPC, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—JSON-RPC, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from distributed systems and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent

The structural core consists of a carrier, A request carries version, method, parameters and optional id; the server returns a matching result or structured error, while omission of id denotes a notification with no response., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of JSON-RPC, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: JSON-RPC, carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in distributed systems.

The proposed strict upward parent is prime:interface. The protocol defines a machine interface between remote callers and methods; JSON message correlation supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while JSON-RPC adds domain-specific constraints.

The entry does not collapse into that parent because minimal JSON wire semantics for RPC independent of HTTP or another transport It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of JSON-RPC. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge.

The prospective workspace queue contains one strict upward edge to prime:interface. No live DAG mutation is authorized.

Relationships to Other Abstractions

Local relationship map for JSON-RPCParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.JSON-RPCDOMAINPrime abstraction: Interface — is a kind ofInterfacePRIME

Current abstraction JSON-RPC Domain-specific

Parents (1) — more general patterns this builds on

  • JSON-RPC is a kind of Interface Prime

    The proposed strict upward parent is prime:interface.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

JSON-RPC sits in a moderately populated region (57th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Messaging Protocols & Networked Services (23 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With

  • REST. REST organizes resource representations through uniform interface semantics, commonly HTTP; JSON-RPC exposes named remote procedures and can run over many transports.
  • One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
  • Measurement or implementation of JSON-RPC. A proxy or realization is evidence for the abstraction, not the abstraction itself.
  • Generalized JSON-RPC. An extension qualifies only when its changed axioms and retained invariant are stated.

Notes

[n1] Source cited in the frozen article, 'specification - JSON-RPC - Trac'. ↩a ↩b

[n2] Source cited in the frozen article, 'JSON-RPC 2.0 Specification'. ↩a ↩b

References

[1] https://modelcontextprotocol.io/docs/learn/architecture. registry ↩