快速开始Quick start
在首页“接入”中选择你使用的客户端，按对应步骤添加 PeopleRouter。MCP 地址：https://mcp.peoplerouter.ai。
Choose your client in the homepage connection guide and add PeopleRouter. MCP endpoint: https://mcp.peoplerouter.ai.
支持 OAuth 的客户端会引导你登录 DINQ 并授权；脚本和后端集成可在控制台创建 API Key，通过 Authorization: Bearer <DINQ_API_KEY> 请求头传入。不要把 Key 发到聊天里。
For OAuth clients, sign in to DINQ and authorize access. Scripts and backend integrations can create an API key in the console and send it as Authorization: Bearer <DINQ_API_KEY>. Keep the key out of chat.
连接后先让 Agent 调用 capabilities 查看当前能力与价格，再描述你的需求。例如：“找在新加坡、有大模型推理优化经验的工程师，附上项目经历与匹配依据。”
After connecting, ask your agent to call capabilities for current capabilities and pricing, then describe your goal. For example: “Find engineers in Singapore with LLM inference optimization experience, including relevant projects and reasons for the match.”
使用指南User guide
人才搜寻：说明岗位、地区、技能、行业与经验要求。可提供公司、仓库或论文链接，帮助 Agent 确定搜索范围。要求结果附上公开主页与匹配理由。
Talent search: specify role, location, skills, industry and experience. Company, repository or paper links can narrow the search. Request public profiles and reasons for each match.
达人筛选：说明平台、城市、内容主题和受众要求。例如为赣州西餐厅寻找探店达人，再核实近期内容和可获取的账号数据。
Creator discovery: specify platform, city, content theme and audience requirements. For example, find restaurant creators in Ganzhou, then review recent content and available account data.
资料补全：提供已知人物主页、账号或公司域名，补充任职、公司背景和相关公开资料。关联账号时要求展示身份匹配依据。
Profile enrichment: provide a known profile, account or company domain to retrieve available work history and company context. Ask for matching evidence when linking accounts.
联系方式：提供姓名与公司或已知主页，查找可获取的工作邮箱；需要时验证邮箱。资料来源、未知字段与验证状态应分别标明。
Contact discovery: provide a name and company or a known profile to look for an available work email; verify an address when needed. Distinguish sources, unknown fields and verification status.
Agent 应先查看 capabilities；平台专属需求先用 find_tool 查找接口，再用 endpoint 阅读所需参数与价格。根据实际能力执行，不把未查询的信息写成结果。
Agents should inspect capabilities first. For platform-specific tasks, use find_tool to discover endpoints, then endpoint to read inputs and pricing. Use available capabilities and do not present unqueried information as results.
接口、计费与错误处理APIs, pricing and errors
接口目录列出具体接口；核心能力目录按任务聚合供应商。参数和可用性会更新，以实时目录和 MCP 工具返回的 schema 为准。
The API directory lists individual endpoints; the capability catalog groups providers by task. Inputs and availability can change; use the live catalog and MCP tool schemas.
capabilities 与 endpoint 用于了解能力和接口。搜索与补全接口根据输入返回数据；能力工具的响应包含 outcome、output、plan 和 _dinq.tried，分别用于判断结果、读取输出、查看路由与调用记录。具体接口的返回字段请查看对应说明。
capabilities and endpoint describe the available capabilities and endpoints. Capability tool responses include outcome, output, plan and _dinq.tried for status, data, routing and attempts. Consult the individual endpoint for its response fields.
调用前查看对应接口的积分价格与计费单位，调用后在控制台查看余额和记录。费用与成功条件依接口而异，不默认所有空结果都免费。
Review credit prices and billing units before calling; inspect balance and usage in the console afterwards. Billing and success conditions depend on the endpoint; do not assume every empty result is free.
授权失败时先检查登录状态或 API Key；参数错误时对照 schema 修正；没有结果时调整条件或查看其他可用来源。outcome 为 error 时读取实际错误码与信息，不把失败当作无匹配。
For authorization failures, check sign-in or the API key. For input errors, correct inputs against the schema. For no matches, revise filters or inspect other sources. When outcome is error, read the actual code and message rather than treating failure as no match.