AI Support¶
This section collects everything an AI agent or LLM tool needs to integrate with JustLend DAO: machine-readable documentation endpoints, the MCP server, JustLend Skills, and a compact AI/RAG documentation set.
In this section¶
| Page | Use for |
|---|---|
| AI / LLMs | Machine-readable entry points — llms.txt, llms-full.txt, OpenAPI YAML, contracts.json, JSON ABIs — and which to use when. |
| MCP Server | Install and run the JustLend MCP server (59 tools): account analysis, market queries, transaction pre-flight, and wallet-aware writes with HITL confirmation. |
| JustLend Skills | The JustLend Skills package (9 read-only tools) for agent frameworks. |
| AI Docs for Agents | Compact, RAG-oriented pages: source-of-truth routing, market/account/workflow guides, MCP safety policy, English/Chinese FAQs, and the full MCP tool catalog. |
Machine-readable sources of truth¶
Prefer these over rendered HTML when integrating programmatically:
- OpenAPI 3.1 spec — public read-only HTTP API contract (base URL
https://openapi.just.network). contracts.json+contracts.schema.json— deployed addresses in Base58 / EVM hex / TRON hex, withactive/legacystatus.- JSON ABIs — interface definitions for contract calls and event decoding.
- MCP tools — for any wallet-aware action; side-effect annotations and HITL confirmation apply.
Choosing between API, MCP, and contracts¶
For task-by-task routing (e.g. "what markets exist", "this address's health factor", "supply for me", "is this transaction safe"), follow the Source of Truth decision guide. As a rule of thumb:
- Read-only HTTP integration → OpenAPI spec /
/lend/*endpoints. - Agent workflows and wallet actions → MCP server tools.
- Addresses and ABIs →
contracts.json+/developers/abis/. - Concepts and risk context → the human documentation pages.