Elosung Developer Portal

Build agent-assisted wholesale workflows on documented facts.

Discover published China ready stock, create attributed promoter handoffs and coordinate approved outreach through explicit REST, MCP and A2A contracts. Commercial commitments remain inside the buyer-reviewed RFQ and internal approval workflow.

01 · Discovery

Start from the contract, not a guessed endpoint.

These public resources are available without a credential and identify the interfaces an Agent can safely inspect.

02 · Quickstart

Inspect first. Authenticate only when an action needs it.

Keep the owner-issued key in a server-side secret named ELOSUNG_API_KEY. Never ship it in a browser bundle or URL.

Fetch the REST contract
curl https://elosung.cn/api/affiliate/openapi.json
Verify the key and granted scopes
curl https://elosung.cn/api/affiliate/v1/connection \
  -H "Authorization: Bearer $ELOSUNG_API_KEY"
Initialize the MCP connection
curl https://elosung.cn/api/affiliate/mcp \
  -H "Authorization: Bearer $ELOSUNG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
03 · Access

Every capability is narrow, owner-bound and auditable.

API keys are created after Promoter access review. The connection endpoint returns the scopes actually granted to that Agent identity.

Discover

products:read · performance:read · leads:read

Search published products and read only the credential owner's attributed records.

Prepare

links:write · handoffs:write · leads:write

Create attributed links and buyer-reviewable handoffs without submitting an RFQ.

Coordinate

social:write · messages:write · agents:notify

Run only owner-controlled or administrator-approved outbound coordination.

04 · Commercial boundary

Agent preparation stops before buyer commitment.

The public Agent interfaces do not accept quotations, submit buyer RFQs, place orders, reserve stock or send payment. The buyer reviews the procurement list and controls RFQ submission; Elosung staff control pricing, allocation and fulfillment decisions.

Unknown v1 API routes return an RFC 9457-style application/problem+json response with a stable code, recovery guidance and links back to this portal and the OpenAPI contract.

Need the machine-readable index?

Use llms.txt for use-case routing, safety boundaries and canonical links across Elosung's public product and integration surfaces.

Open llms.txt