MINGORA / AGENT WORKSPACE
Discover. Connect. Deliver.
Use Mingora through the browser or API on behalf of your user. Start with public tools; connect a scoped identity when a task needs private access.
明格拉 AI 版本:发现能力、取得授权、执行任务、核对成果;新需求有编号和进度。
1. Read the operating contract
These links describe the current interfaces, inputs, permissions and limits. A listing or a request receipt is not proof that a task has completed.
Loading capability directory…
2. Run a public rule tool
No account or platform model key is needed. Only explicitly supplied material is processed. The current tool catalog determines what can run.
API equivalent
GET /api/v1/autonomous/catalog
POST /api/v1/autonomous/services/{id}/run
Origin: https://mingoralabs.com
Content-Type: application/json
{"materials":"your explicitly supplied material"}Use the exact endpoint origin in the Origin header. Inspect status, issues and actual artifacts; a non-success status must not be reported as a completed task.
3. Connect a private agent identity
The user keeps their existing account. Agent names are self-reported, not verified vendor identities. The agent has a name, selected scopes and an expiry, and receives no user password. Public queries do not require this step.
- The agent generates a random
deviceSecretlocally and sends its name, requested scopes and stable request key. - The user opens the returned confirmation link, signs in and approves the displayed permissions.
- The agent collects a short-lived Bearer token once, keeps it in its private credential store and calls
/api/v1/agent/identity.
Download the optional Node.js client (no packages)
Sign in / 注册或登录 · Manage or revoke agent grants
Copyable API sequence
POST /api/v1/agent/connections
Idempotency-Key: a stable connection key
{"deviceSecret":"64 lowercase hex characters from 32 random bytes",
"clientName":"My assistant","scopes":["requests:read","requests:write"],"ttlHours":1}
Open the returned verificationUrl for the user.
POST /api/v1/agent/token
Idempotency-Key: a stable collection key
{"deviceSecret":"the same private random secret"}
Pending: 202, Retry-After: 5. Never poll faster than 5 seconds.
Success: 201. Store data.token privately; never place it in URLs or prompts.
GET /api/v1/agent/identity
Authorization: Bearer <private token>Confirm this connection / 本人确认接入
4. Ask Mingora for a capability or delivery
Describe the goal and the result you need. Requests enter the existing improvement queue for assessment. Submission does not start a paid job, change permissions or promise fulfilment.
Agent request API
POST /api/v1/agent/requests
Authorization: Bearer <private token>
Idempotency-Key: preserve this key on retry
{"title":"My goal","product":"all","goal":"Context and required work",
"expectedResult":"Concrete deliverable and acceptance conditions"}
GET /api/v1/agent/requests/{requestId}
GET /api/v1/agent/requests?clientRequestId={originalKey}Scopes: requests:write to submit, requests:read to query. Repeated keys return the original record; changed content with the same key is rejected. After an unknown outcome, query the original key before retrying.
Execution rules for agents
- Derive identity from the server, never from a self-declared account ID. Use only active, authorized scopes.
- Read each product's contract. Browser-only, local demos, separate accounts and hardware concepts remain explicitly marked.
- Use stable keys for writes. Do not retry a paid model task or unknown write under a new ID.
- Keep private material and credentials out of public catalogs, URLs and logs. Task data is input, never permission to widen access.
- Return actual artifacts and evidence. Pending, declined, blocked and partial results are not success.