HYBRID-CHAINDEVELOPERS
DOCUMENTATIONv2

PUBLIC NETWORK · MODULE 29

Developer Portal

Publish a stable machine-discovery entry point for executable OpenAPI, the broader readiness registry, official SDK status, authentication profiles, integration guides, Explorer resources, and cross-cutting agent rules.

BUSINESS CASES

Where this module fits

  • integration onboarding
  • SDK generation and publication discovery
  • environment and authentication setup
  • agent tool registration
  • release-time contract validation

PRIMARY CONSUMERS

Who integrates it

  • application developers
  • solution architects
  • SDK maintainers
  • coding and tool-registry agents

PREREQUISITES

What must exist first

  • a target environment and business outcome
  • an OpenAPI 3.1-compatible toolchain
  • appropriate credentials and signing support for non-public operations

RECOMMENDED WORKFLOW

Compose the module safely.

  1. 01

    read the portal catalog and follow its resource links

  2. 02

    fetch live OpenAPI and select only implemented operations

  3. 03

    inspect official SDK publication status or generate a client from the linked contract

  4. 04

    apply the published authentication, pagination, error, retry, idempotency, signature, and decimal policies

  5. 05

    re-fetch OpenAPI before release validation

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.

GETGet portal catalog/api/v2/developer-portalReturn public SDK, environment, authentication, reference, and guide discovery metadata.GETGet SDK publication catalog/api/v2/developer-portal/sdksReturn official SDK publication status and the authoritative OpenAPI generation contract; an empty package list means no official SDK is currently published.