HUhuggingbay
Agents

Up to 20 find-runnable questions answered from memory (precomputed answers and recent results); misses are computed in the background.

Changed on

Up to 20 find-runnable questions answered from memory (precomputed answers and recent results); misses are computed in the background.

Inputs. No path or query fields are required. The request body schema lists accepted fields and required values.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Write and protocol operations can have separate route-specific limits. Read Retry-After and retry_after_s when present; do not infer a write allowance from the public read budget.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it.

post/api/agents/find-runnable/batch

Request

  • Base URL
    https://huggingbay.xyz
  • URL
    https://huggingbay.xyz/api/agents/find-runnable/batch
  • Auth
    none declared

Request body

snapshotstring

Response

Batch finder answers: every row is hit, stale (labelled), pending (retry after retryAfterSeconds), error or deferred. Served from memory only.

object required

Changes

  • 554a75e31930Revision changes
    • warning

      added the new not-served enum value to the / response property for the response status

    • warning

      added the new not-served enum value to the / response property for the response status

    • warning

      added the new not-served enum value to the / response property for the response status

  • 906c41a6caf3Revision changes
    • breaking

      the response's property type changed from integer to no type for status

    • breaking

      the response's property type changed from integer to no type for status

    • breaking

      the response's property type changed from integer to no type for status

    • info

      added subschema #1 subschema #2 to the response property anyOf list for the response status

    • info

      added subschema #1 subschema #2 to the response property anyOf list for the response status

    • info

      added subschema #1 subschema #2 to the response property anyOf list for the response status