Relicex
LoginGet started

Relicex docs · Two product paths, one technical layer

Find solutions, or build the asset packs that power them

Relicex does not require everyone to understand the API first. Buyers start with problems and solutions; creators start with asset packs, solution composition, and revenue; technical setup defaults to Relicex Skill, with the API kept for advanced custom integrations.

Start with solutionsRead publish guideRelicex Skill & API
Buyers: problem → solutionCreators: asset pack → solution → revenueTech: Skill first, API advanced

Pick a path

Choose the job you are trying to finish

The docs home keeps two core audiences: buyers and creators. Developers are not treated as a separate top-level persona; technical work belongs to Relicex Skill and advanced API integration.

01

I am a buyer: I need to solve a problem

Start from a problem, need, or scenario. Find a ready solution or request a custom solution from creators.

  • Describe a problem
  • Compare complete and customizable solutions
  • Receive entitlements and deliveries after purchase
Find solutionsUnderstand access and delivery
02

I am a creator: I want to build and earn

Turn knowledge, memory, capabilities, and workflows into asset packs, then sell them directly or compose them into solutions.

  • Publish asset packs
  • Compose solutions
  • Earn from sales and reuse
Open Creator PortalRead revenue model
Skill

I need technical setup: start with Relicex Skill

Most technical setup belongs in Relicex Skill: generating manifests, preparing packages, and connecting Agent runtimes. Use the API when you have custom integration needs.

  • Skill handles default packaging
  • Manifest describes asset boundaries
  • API serves advanced integrations
Connect Relicex SkillRead API reference

Quick start

The shortest way to understand Relicex

Think of Relicex as a two-layer platform: buyers find solutions on the surface, while creators use reusable asset packs to power solutions and revenue underneath.

01

Buyers start by describing a problem

Search or open a solution page, then judge fit, price, deliverables, and customization options first.

02

Creators start by packaging reusable assets

Asset packs can be memory, experience, or capability units that carry knowledge, workflows, abilities, and runtime requirements.

03

Technical setup starts with Skill

Relicex Skill generates manifests, prepares packages, and connects runtimes; the API is for custom systems.

04

Purchases create access and settlement

Checkout creates entitlements and deliveries; reused asset packs flow into settlement and royalty records.

Relicex Skill

Relicex Skill is the default technical entry; the API is advanced

We do not make developers a third top-level audience. Technical creators, Agent engineers, and external integrators can start with Relicex Skill to understand the default flow. Use the API only when you need custom discovery, checkout, entitlement, settlement, or MCP integrations.

Generate manifestsPrepare package.zipConnect Agent runtimesRequest accessDownload deliveriesAdvanced API integration
Open Relicex SkillAdvanced API reference
Minimal Relicex Skill environment
export RELICEX_AGENT_TOKEN="amt_xxx"

# Optional overrides for local development / self-hosting:
# export RELICEX_API_BASE_URL="https://relicex.com/api"
# export RELICEX_SITE_BASE_URL="https://relicex.com"
# export RELICEX_DEFAULT_LOCALE="en"

Core concepts, with fewer terms upfront

Do not start by memorizing the whole platform. These six concepts explain the buyer experience, creator revenue, and technical integration layer.

problem / need

What the buyer actually wants to solve; the entry point for search and customization.

solution

The buyer-facing transaction unit. It can be purchased directly or customized.

asset pack

The capability layer of Relicex. It can be sold directly or reused inside solutions.

package / manifest

The technical container and capability boundary for an asset pack, usually assisted by Skill.

entitlement

The access right granted after purchase, pointing to a solution or an asset pack.

settlement

Records for solution sales, asset sales, reuse royalties, and payouts.

Two core workflows

Do not force every concept into one flow. Buyers and creators start in different places, then converge at checkout, entitlement, delivery, and settlement.

Buyer: problem to solution

  1. Describe a problem or search a scenario
  2. Discover complete / customizable solutions
  3. Inspect supporting asset packs
  4. Quote / checkout
  5. Receive entitlements and delivery
  6. Give match feedback or request customization

Creator: asset pack to revenue

  1. Organize reusable knowledge, experience, or capability
  2. Use Relicex Skill to generate package / manifest
  3. Publish to the Asset Library
  4. Compose your own solution or allow reuse
  5. Earn from asset sales, solution sales, and reuse royalties
  6. Track settlement and payouts in Creator Portal

What to read next

Enter by task instead of trying to read the entire platform model at once.

Solution marketplace

Start from a problem or need and inspect purchasable or customizable solutions.

Publish guide

Use Relicex Skill and the web workflow to publish knowledge, experience, or capability as an asset pack.

Revenue model

Understand asset sales, solution sales, asset reuse royalties, and payouts.

Advanced API reference

Use API workflows when you need custom systems, Agents, or MCP integrations.

Manifest spec

Understand how an asset pack describes capability boundaries, runtime needs, and access behavior.

Package authoring

Understand package.zip structure and how Skill or custom flows prepare packages.

Download combined spec MD

Safety and commercial defaults

Relicex Skill and API integrations should stay conservative by default: no automatic payment, no automatic public publishing, no automatic execution of capability code, and no unlimited asset reuse from a solution purchase.

Paid solution or asset access returns a human confirmation or payment requirement instead of auto-purchasing.
Asset-pack drafts generated by Skill should still be reviewed by a human before public publication or solution composition.
capability_pack code is not executed by default; inspect manifest, README, permissions, input/output contracts, and evaluation first.
Never pack API tokens, private keys, cookies, passwords, or credentials into asset files.

Relicex

Start with one path

Buyers can find solutions; creators can build and earn; technical details live in Relicex Skill and API docs when needed.

Find solutionsOpen Creator Portal