Capability service access guide

01

Prepare a creator service

Choose a prompt, Skill, Agent, or workflow you have the right to publish. Define its task, inputs, outputs, and limitations. Sell access to the capability; core prompts, code, and workflows are not buyer deliverables.

Prepare a version, public description, access scope, runtime responsibility, and cost statement. Public descriptions must not contain core assets or credentials. Publishing, pricing, and settlement require product entries and service terms. This guide is not a publishing form.

02

Open your account

Open the User Console and use the site's sign-in flow. New accounts follow the available registration or Team invitation path.

Without a registration entry, obtain an invitation from the site or Team administrator. Signing in does not grant a specific model, free allowance, publishing eligibility, or Team-management rights.

03

Check services and costs

Review account-visible services, model names, access details, plans, balance, and allowance. Check prices, charging units, periods, included usage, and limits.

Catalog visibility is not permission to make every request. Creators need to account for model and service operating costs. Revenue is not profit or a withdrawable balance.

04

Create your API key

Use the console's API-key page to create a calling credential. It authorizes model calls, not management operations.

Store the credential in protected client configuration. Do not place it in Git, screenshots, conversations, or this page. Revocation stops future use.

05

Configure your client

Choose an application or Agent client that supports the protocol. Enter the public service address, your API key, and the public model name from your account's instructions.

The code-review example on the home page describes a service model, not a model ID to paste. Calls require valid access rights. This guide installs no MCP server and changes no local configuration.

06

Verify delivery

Send a request with non-sensitive input. Check the agreed output, request history, usage, and consumption records.

Output, request, and bill should identify the same call. A timeout or disconnected client does not prove zero usage. Creator commercialization requires paid use and delivery evidence, not sign-in counts.

Three client configuration fields

Service address

The public API address for the selected protocol, not an internal runtime address.

API key

Your valid calling credential, not an administrative credential.

Model name

An account-visible public model name, not a home-page example or internal target.

When you cannot proceed

No publishing or offering entry

Review service activation, publishing eligibility, and commercial terms. Neither sign-in nor a running component establishes sales permission.

Sign-in failed

Use the login page's feedback, password recovery, or Team invitation flow. This site does not collect passwords.

Missing access or allowance

Check account rights, plans, balance, and service terms. Contact an authorized administrator. Do not rotate keys to bypass a restriction.

Request failure or timeout

Keep a redacted timestamp, protocol, model name, and request ID. Review request history. Do not share credentials, request bodies, or raw error dumps.