Agent Execution Contract Intelligence API
Check caller-supplied OpenAPI documents, JSON Schemas, and workflow definitions for missing expiry, retry, idempotency, pagination, error, output, state, and partial-failure rules that make an agent fail or repeat a call.
Find presigned URLs and access tokens in caller-supplied operations that do not state a lifetime, and sentences that both expire and never expire. A missing lifetime is undocumented, not a live-server defect.
Read caller-supplied retry sentences and timeout statuses. A timeout with no retry sentence is missing documentation. The HTTP method is not treated as safe or unsafe to retry.
Find create or update sentences that do not name an idempotency key or a replay result. The check does not call an operation idempotent unless the supplied text says so, and POST alone is not proof of a write.
Find page or cursor operations in caller-supplied OpenAPI or tool definitions that omit the next-page field, the end condition, or which of cursor and offset to follow.
Check whether caller-supplied 4xx and 5xx responses name a code, message, or field an agent can correct. A missing error schema is undocumented, not proof the server never fails.
Compare caller-supplied success examples with their output schemas for type, enum, required fields, and extra properties. A mismatch is a conflict between those documents, not a confirmed live response.
Find supplied workflow transitions that name an unknown state, two destinations for one trigger, or an operation that is not in the supplied list. Missing edges are undocumented, not proof a state is unreachable.
Find multi-step workflows that do not say whether a later failure leaves earlier steps in place, rolls them back, or can be retried. Atomic and partial success in the same text is a contract contradiction.