ReferenceAI skillsPermissions, approval, and limits

Permissions, approval, and limits

Use when permissions, approval, or usage limits block progress.

Skill version: 1.0.0. Resource: skill://nadoobio-account-and-approval/SKILL.md.

Before reading customer data, use get_connection_context to check the connected account, organization, and scopes. Public listing is not proof of authentication. legacyUnscoped denotes legacy role permissions; this lookup does not authorize project access or execution. Web links recheck the browser's current account. If the account or organization differs, switch in the browser and reopen the same URL.

ErrorMeaningWhat to tell the user
authentication_requiredValid authentication has not been confirmed.Ask the user to issue and configure an API key in Nadoo Bio.
scope_required (required)The key lacks the required scope.Explain the required scopes: catalog:read, jobs:read, plans:write, jobs:submit, and files:write.
agent_execution_disabledAI-agent plan creation and submission through API keys are disabled by the platform administrator. This is not a key or project-permission issue.Do not repeat the request. Direct the researcher to create a plan in the UI or ask the platform administrator to enable AI-agent execution. Read tools remain available.
not_found / plan_unavailableThe resource does not exist or is not accessible.The response intentionally does not distinguish these cases. Ask the user to check the identifier and project; do not try guessed alternatives.
plan_not_approvedHuman approval is missing or expired.Share the approval link and check the returned approval policy. An individual API-key plan can wait indefinitely for approval, but requires explicit submission within 15 minutes after approval. Approval alone neither resumes the agent nor submits a job.
The desired tool is missing from execution options.Absence from the list does not establish the cause.Read reason, reasonText, workflowSupport, and the document at supportDocPath, then explain which input-preparation and validation steps are available now.
runtime_consumer_unavailableThe platform lacks the required execution worker (fixableBy: platform).Explain that this is not a permission or key issue, and suggest input preparation and validation as the next steps.
release_unavailableNo release is published for this organization (fixableBy: organization-operator). Releases apply organization-wide, so its projects share this status.Relay reasonText unchanged and suggest two next steps: prepare and validate inputs, and ask an authorized organization operator to publish a release.
session_submission_requiredOnly plans created in the current web session can be submitted.Suggest creating a new plan in the web UI only when this reason is actually returned. Approving an API-key plan or adding scopes does not resolve it.
monthly_limit_exceededThe monthly job-count allowance is exhausted.Report used, limit, remaining, and the response's recoveryBoundary.submissionDeadline (this plan's submission deadline), then stop. This is a job-count limit, not a monetary charge. The reset time is unknown. After the deadline, use rerun_plan to create a new plan requiring new approval. This plan can be submitted only if the allowance is adjusted before its deadline. Report the deadline itself rather than calculating remaining time.
context_changedThe selected organization has changed.Ask the user to return to the original organization in the product UI.

Rules to follow

  • Relay the returned approval or permission reason as given. Continue using the same key, project, and user's own plan.
  • Do not write API keys, cookies, or tokens in conversations or files.
  • Product links (create_view_link) are generated after rechecking permissions. Do not create or request download-credential URLs.

list_candidate_inputs reads the user's own records with jobs:read; it does not grant permission to save preparations or plans. Returned list and detail links return to the same URL after login and recheck the browser's current account, organization, and project permissions. API-key authentication and browser login are separate; never place keys or cookies in URLs.

Preserve each link's snapshotId and payloadHash. Do not remove hashes or switch to the latest input on hash conflicts or permission errors. sourceStatus=unavailable means the record's current source is unavailable; do not promise that signing in again will resolve it. A candidate input's web-session-required directs the user to save a preparation plan on the web. Reissuing a key or approving it cannot remove a preparation plan's submission block.

Login and keys for paid delegation

Review delegation documents through browser login and submit through MCP using the API key named in the document. Successful browser login does not configure the key or restore the original approving session. A different session may allow viewing history while prohibiting new consent or submission requests. Do not promise that signing in again restores an expired, revoked, or context-changed approving session.

If get_job returns scope_required after a receipt from submit_delegated_plan, distinguish missing jobs:read from failed submission. Preserve the original receipt and request key, and share the returned job link. Do not replace the key to reuse a delegation. agent_delegation_runtime_not_connected means delegated execution is not connected for that model; adding scopes or signing in again cannot resolve it.

On this page