Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gearsnakes Review-Only Inquiry API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgearsnakes-field-ops-public.netlify.app%2Fgearsnakes-field-ops-public" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgearsnakes-field-ops-public.netlify.app%2Fgearsnakes-field-ops-public" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Gearsnakes Review-Only Inquiry API.
Check whether review-only inquiry intake is currently available before submitting
Submit a field-task inquiry with a title, category, city, details, contactEmail, and requester for owner review
Retry an uncertain submission safely by resending the identical body with the same Idempotency-Key
Classify a request into a category such as Courier pickup and delivery, Field verification, or Photo and video documentation
GET STARTED
Patterns agents use Gearsnakes Review-Only Inquiry API for, with concrete tasks.
★ AI assistant forwarding a field-task request
An AI assistant handling a user's request for an in-person errand can hand it to Gearsnakes for human review. Through Jentic the agent searches for 'submit a field task inquiry', calls GET /api/requests to confirm intakeAvailable, then posts the inquiry to POST /api/requests with a fresh Idempotency-Key. A 202 response means the inquiry is stored for review and no work has been accepted yet, which the agent reports back to the user plainly.
Call GET /api/requests, and if intake is available POST /api/requests with an Idempotency-Key, category 'Document transfer', city 'Austin', a title, details, contactEmail, requester, authorizedToRequest true, and reviewOnly true
Field verification inquiry
A business that needs someone to confirm a site, an address, or the state of equipment can describe the job in up to 2000 characters of details and submit it under the Field verification or Equipment assistance category. The spec asks callers to keep personal credentials, payment information, attachments, and sensitive site access details out of the request, so the inquiry carries the scope only and the owner follows up by email.
POST /api/requests with category 'Field verification', a title of at least 8 characters, a city, details of at least 20 characters describing the site, contactEmail, requester, authorizedToRequest true, and reviewOnly true
Safe retries for uncertain submissions
Network failures and 503 responses leave a client unsure whether an inquiry landed. The API replays the original receipt with a 200 when the identical body and Idempotency-Key are resent, returns 409 if a key is reused for a different inquiry, and answers 429 when the review queue or request limit is reached, so a client can retry without creating duplicates.
After a 503 from POST /api/requests, resend the identical JSON body with the original Idempotency-Key and treat a 200 as the replayed receipt
2 endpoints — the gearsnakes review-only inquiry api accepts unverified requests for local field tasks, such as courier pickup and delivery, field verification, document transfer, equipment assistance, and photo and video documentation, and holds them for the owner to review.
METHOD
PATH
DESCRIPTION
/api/requests
Check inquiry intake availability
/api/requests
Submit an inquiry for owner review
/api/requests
Check inquiry intake availability
/api/requests
Submit an inquiry for owner review
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Gearsnakes by hand means generating and persisting an Idempotency-Key per inquiry, enforcing the field length rules, and handling 409, 429, and 503 retry semantics yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it with the input schema in hand.
Permission scoping
Gearsnakes exposes one path with two methods and carries the inquiry in the request body, so rules bound which operations your agent may call, not which inquiries it sends. You choose the operations it may call, so the submit operation is not included unless you add it.
Credential isolation
Gearsnakes needs no account or API key for its inquiry intake. For any API you add that does use a key, your own Jentic One instance keeps it encrypted and injects it at execution time so it never reaches the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'request a courier pickup' or 'submit a field task inquiry', and Jentic returns the matching Gearsnakes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Gearsnakes Review-Only Inquiry API through Jentic.
Does the Gearsnakes Review-Only Inquiry API require authentication?
No API key or account scheme is declared in its OpenAPI spec, and the global security list is empty. Submissions do require an Idempotency-Key header of 16 to 128 letters, digits, underscores, or hyphens, which identifies the request for safe retries rather than authenticating the caller. The spec notes that cross-origin browser requests are denied with a 403.
Does submitting an inquiry book the work?
No. A 202 from POST /api/requests means the inquiry is durably stored for owner review and no work is accepted. The spec states the API handles unverified inquiries only, with no payments, agent enrollment, assignment acceptance, or dispatch, and both authorizedToRequest and reviewOnly must be sent as true.
What are the rate limits for the Gearsnakes Review-Only Inquiry API?
Per the POST /api/requests description in the spec, submissions are limited to five requests per minute per IP or domain and 100 unique inquiries per UTC day, with an 8 KB maximum body. A 429 response means the review queue or request limit has been reached.
Is there a Gearsnakes MCP server?
You don't need an MCP server to give your agent the Gearsnakes Review-Only Inquiry API. Jentic connects it directly from the API Directory: import it and your agent can check availability and submit inquiries, with each operation discovered on demand rather than preloaded into its context.
Can I limit what my agent is allowed to do with the Gearsnakes API?
Yes. For example, write a rule that allows only GET /api/requests, so the agent can report whether intake is open but cannot submit an inquiry on your behalf until you add POST /api/requests to the allowed set. Every call it makes is logged.
How do I submit an inquiry through Jentic?
Add the Gearsnakes Review-Only Inquiry API to your Jentic One instance from the directory. Your agent searches for 'submit a field task inquiry', loads the submitInquiryForReview operation, and posts the required fields with an Idempotency-Key header. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Check whether Gearsnakes is accepting field-task inquiries and submit a review-only request for courier, field verification, document transfer, equipment, or photo work.
Use for: Check whether Gearsnakes is accepting inquiries right now, I need to request a courier pickup in a specific city, Submit a field verification request for owner review, I want to ask for photo documentation of a site
Not supported: Does not handle payments, job dispatch, assignment acceptance, or worker enrollment. Use for checking intake availability and submitting review-only field-task inquiries only.
The Gearsnakes Review-Only Inquiry API accepts unverified requests for local field tasks, such as courier pickup and delivery, field verification, document transfer, equipment assistance, and photo and video documentation, and holds them for the owner to review. A client first checks whether intake is open, then submits a structured inquiry with a title, category, city, details, contact email, and requester name, plus explicit authorizedToRequest and reviewOnly confirmations. Submissions are idempotent through a required Idempotency-Key header, and an accepted inquiry is stored for review only: the API does not take payments, enroll agents, accept assignments, or dispatch work.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>