Get portal catalog

/api/v2/developer-portal

AUTHENTICATIONNone · publicAUTHORITATIVE OWNERdeveloper-platformCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Return public SDK, environment, authentication, reference, and guide discovery metadata.

WHEN THIS CALL IS USEFUL

Start every human or agent integration here to discover current machine-contract, readiness-registry, guide, Explorer, SDK, authentication, and operational-policy resources.

OUTCOME · Discover

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover portal catalog.
Gives human and agentic integrations one discoverable path from service identity and reference data to executable OpenAPI, capability ownership, guides, SDK status, and request-signing controls.

ISOLATION + AUTHORITY

Public service metadata, the OpenAPI document, the capability registry, guides, SDK listings, bearer credentials, step-up grants, and request-signing keys are separate artifacts. Discovery metadata grants no tenant, wallet, custody, payment, settlement, publisher, matching, or trading authority; public signing-key metadata never includes private key material.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve whether the caller needs public discovery, bearer authorization, purpose-bound step-up, or RFC 9421 request signing; do not substitute one mechanism for another.

WHAT TO DO NEXT

Follow the returned authoritative OpenAPI, capability, guide, or SDK link appropriate to the integration task.
Validate executable behavior against deployed OpenAPI rather than inferring it from narrative guidance or package names.

AGENT GUIDANCE

Use portal catalog only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Treat deployment identity, OpenAPI schema, capability readiness, guide narrative, SDK publication, bearer authorization, step-up authorization, and request-signing proof as distinct inputs; none substitutes for another.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

RESPONSES

Status and payload examples

200Machine-discovery root for reference authority, authentication profiles, agent integration rules, and public developer resources.Read completed · JSON RESPONSE+

{
  "baseUrl": "https://api.hybrid-chain.com/api/v2",
  "currentVersion": "v2",
  "legacyVersion": "v1",
  "authentication": [
    {
      "id": "public",
      "principal": "anonymous",
      "credential": "none",
      "lifetimeSeconds": null,
      "requestSigning": "not applicable"
    }
  ],
  "resources": [
    {
      "rel": "openapi",
      "href": "/api/v2/openapi.json",
      "mediaType": "application/vnd.oai.openapi+json;version=3.1",
      "description": "Implemented Rust gateway contract only."
    },
    {
      "rel": "capabilities",
      "href": "/api/v2/capabilities",
      "mediaType": "application/json",
      "description": "Complete implemented and planned operation registry."
    },
    {
      "rel": "guides",
      "href": "/api/v2/integration-guides",
      "mediaType": "application/json",
      "description": "Versioned business implementation blueprints."
    }
  ],
  "applications": 45,
  "operations": 832,
  "implementedOperations": 470,
  "referencePolicy": {
    "implementedAuthority": "/api/v2/openapi.json",
    "plannedAuthority": "/api/v2/capabilities",
    "implementationRule": "An operation is implemented only when it appears in OpenAPI and its registry status is implemented-contract.",
    "runtimeRule": "Authentication, scope, tenant, feature, owner-adapter, and downstream-readiness policy still fail closed."
  },
  "agentIntegration": {
    "errorEnvelope": "Branch on HTTP status plus stable code, never message text.",
    "pagination": "Return opaque cursors unchanged with the same filters.",
    "idempotency": "Reuse one key and byte-equivalent request only for retries of one logical mutation.",
    "requestSigning": "Use RFC 9421 Ed25519 and RFC 9530 Content-Digest when required by OpenAPI.",
    "retryPolicy": "Retry only transient failures with bounded backoff, jitter, and reconciliation.",
    "decimalPolicy": "Preserve amounts, prices, quantities, rates, and large identifiers as strings unless the schema says otherwise."
  }
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then follow the returned authoritative OpenAPI, capability, guide, or SDK link appropriate to the integration task.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.

OPERATIONAL NOTES

Security and lifecycle guarantees

Start every integration here and follow resources[].href instead of constructing neighboring paths or scraping the website.
referencePolicy distinguishes executable OpenAPI from the broader readiness registry. Portal counts describe the catalog snapshot; they are not authorization or runtime availability guarantees.
Apply agentIntegration rules for stable error branching, opaque pagination, byte-equivalent idempotent retries, RFC 9421 signing, bounded retries, and precision-safe decimal strings.
No bearer, query parameters, or request body are accepted. The public response is cacheable for 300 seconds; re-fetch after that boundary or before release validation.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗