lidian

Discover compatible endpoints and consume them with structured JSON parameters.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LidianAI/skills --skill lidian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lidian
Source: https://github.com/LidianAI/skills/tree/main/lidian
Command: npx skills add https://github.com/LidianAI/skills --skill lidian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamline the process of outsourcing compute, inference, and external API execution by automatically discovering candidate endpoints and consuming them with structured parameters, reducing custom integration work.

Core Features & Use Cases

  • Endpoint discovery: use discover to fetch compatible endpoints for a given task.
  • Endpoint consumption: use consume with a selected endpointId and JSON params, including authentication and balance handling.
  • Guided workflow: follows the Discover -> Consume contract with optional recovery via account and feedback for quality tracking.
  • Use Case: Automate third-party data retrieval, model inference, or compute tasks by routing requests through Lidian instead of hard-coding integrations.

Quick Start

Identify a task, run discover to fetch candidate endpoints, then run consume with the selected endpointId and a JSON params payload.

Frequently Asked Questions about lidian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate API calls without hard-coding integration details?

Automate API calls without hard-coding integration details by using a discover step to fetch compatible endpoints for a task, then passing structured parameters to consume the selected endpoint. This enforces a discover-to-consume contract.

What is endpoint discovery and consumption for outsourcing compute?

Endpoint discovery and consumption for outsourcing compute is a workflow that fetches candidate API endpoints for a task, then executes a consume call with structured JSON parameters, handling authentication and balance checks automatically.

How do I route third-party inference requests dynamically instead of updating static integrations?

Route third-party inference requests dynamically by discovering optimal endpoints for your task and consuming them with structured parameters. This bypasses static integrations and manages payments and error recoveries during execution.

Can I handle API authentication and balance checks automatically during endpoint consumption?

Yes, you can handle API authentication and balance checks automatically during endpoint consumption. The workflow manages these elements natively alongside error recovery when you execute a consume call with structured JSON parameters.

What are the limitations of using a discover and consume contract for external API execution?

Limitations of using a discover and consume contract include relying on available candidate endpoints for your specific task and requiring structured JSON parameters to execute the consume call, with optional recovery needed for quality tracking and error handling.