Every button calls an API operation.

The REZICS website calls this API too. Your code sends an HTTP request, and an AI agent calls a tool through an MCP server. Both reach the same operation.

On warm white paper, three paper strips extend from above, the right, and below. Their ends meet beneath one square of deep blue-gray paper.

Three ways in

Three ways in. One response.

When you select “Export library” in your library, the website sends this request. Your code and agent send the same request, pass the same checks, and receive the same library export.

  • You

    Select “Export library” on your REZICS library page.

  • Code

    GET /v1/me/library-export
      ?actingSubject=…&limit=20
    Authorization: Bearer …
  • Agent

    {
      "name": "library_export",
      "arguments": {
        "query": {
          "actingSubject": "…",
          "limit": 20
        }
      }
    }
    Arguments for tools/call. You choose the identity.

One operation

operationId
  getV1MeLibrary-export
profile
  rezics-library-export-v1

The REZICS website never accesses the database directly. Every read and write goes through the API; anything you can do on the site is available through the API.

Rules

The same rules from every entry point

  • One identity

    actingSubject

    Each write states which identity is acting. A token does not choose for you, and the server checks the identity every time.

  • One permission limit

    scope

    An app or agent can have fewer permissions than the user, never more.

  • One receipt

    Idempotency-Key

    Writes include an idempotency key. Retry the same request after a timeout to get the original result without repeating the operation.

  • One error format

    application/problem+json

    Failures return problem details with a fixed code field. Your code can handle the code without parsing the message.

Index

An index for tools others build

REZICS also indexes other people’s MCP servers, skills, and APIs, with versions, sources, measurements or usage records, ratings, and discussions.

Build your tools on one API.

Use your own code to read and write works, library entries, and community data. Every operation follows REZICS identity and authorization rules.