How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Relm

Relm Discovery API

Self-describing schema, usage, settings.

Documentation Provider Profile APIs.io OpenAPI GitHub

Relm Discovery API is one of 16 APIs that Relm publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Discovery. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and rate-limit docs.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 0.17.1.

Requests are made against a single base URL, https://api.relmcrm.com/v1.

4 operations 3 paths 4 schemas 3 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.17.1
Base URL
https://api.relmcrm.com/v1
Authentication
HTTP Bearer, OAuth 2.0
Contact
Relm
License
Proprietary
Resource Areas
1

Authentication & Security 2

Relm Discovery API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • bearerAuth — Workspace-scoped API key. relmlive... (live) or relmtest... (free, isolated test mode). Mint at https://app.relmcrm.com/.
  • oauth2 — OAuth 2.1 with PKCE (S256) and dynamic client registration (RFC 7591). Live mode only; test mode is API-key only. Discovery: /.well-known/oauth-authorization-s…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

Discovery 4

Self-describing schema, usage, settings.

GET
/schema
Live object/field/enum registry
getSchema → 200default
GET
/usage
Current billing period usage
getUsage → 200default
GET
/settings
Workspace settings (spend cap)
getSettings → 200default
PATCH
/settings
Set the monthly overage spend cap
setSettings body → 200default

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Problem (9 properties), Usage (5 properties), SchemaDoc (4 properties), Settings (1 property). Each schema is shown below with its type and property counts.

Settings
object
1 property
Problem
object
RFC-9457 error. Closed-set rejections carry validoptions + suggestion so an agent self-corrects.
9 properties
SchemaDoc
object
4 properties
Usage
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relmcrm-com-discovery-api-openapi.yml Raw ↑

Other APIs Relm publishes across the network.

Relm MCP Server
AE Profile APIs.io
Relm A2A Agent
AE Profile APIs.io
Relm Activities API
AE Profile APIs.io
Relm Automations API
AE Profile APIs.io
Relm Batch API
AE Profile APIs.io
Relm Companies API
AE Profile APIs.io
Relm Connections API
AE Profile APIs.io
Relm Contacts API
AE Profile APIs.io
Relm Deals API
AE Profile APIs.io
Relm Pipelines API
AE Profile APIs.io
Relm Registry API
AE Profile APIs.io
Relm Search API
AE Profile APIs.io
#Discovery
← Back to R APIs
API Details
ID
relmcrm-com:relmcrm-com-discovery-api
Base URL
https://api.relmcrm.com/v1
Docs
https://relmcrm.com/docs
Provider
Relm
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=relmcrm-com-discovery-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/relmcrm-com-discovery-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Relm Discovery API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.