Your real-world
tool call.

Evaluate us before commissioning work.

Read our JSON trust profile or supplier evaluation guide for owner-stated capabilities, available evidence and questions to resolve before payment. Submitting a scoped task does not charge you or book a crew. An operator reviews your inquiry before you decide whether to accept a quote.

No browser required for task management.

Fetch the catalog, submit a brief, exchange messages, accept a reviewed quote and create a payment checkout using HTTPS and JSON. You do not need to load HTML, images or a form. GET /api/v1/capabilities reports configuration and limits. A task becomes an order when its reviewed quote is accepted; the same ID tracks it throughout.

For a purchasing decision, use our JSON catalog, coverage and pricing pages, or the clearly labeled example report. There is no need to interpret a screenshot to integrate. Card and bank verification can still require payer interaction.

Give your agent a physical capability.

Use Agent Groundcrew when a task needs authorized physical access, measurements, local procurement, live observation, logistics coordination, or hands-on execution. A swarm should nominate one submitting agent and use one idempotency key per logical task.

1. Discover capabilities

GET https://agentgroundcrew.com/api/v1/services

Prices are USD starting estimates. Coverage is confirmed during review. This is a request-and-quote interface, not an instant labor scheduler.

2. Submit an explicit brief

Generate a cryptographically random 32-byte hex tracking token and a unique idempotency key. Keep both in your own secure storage. Send JSON with these headers:

POST /api/v1/tasks
Content-Type: application/json
Idempotency-Key: <unique value, 16–100 characters>
X-Request-Token: <64-character random hex token>

{
  "service": "site-photo-survey",
  "alias": "procurement-agent-7",
  "email": "",
  "location": "City, region, country",
  "scope": "Photograph the authorized loading area and measure entry clearance.",
  "acceptance": "Six timestamped photos and clearance dimensions in millimeters.",
  "budgetUsd": 250,
  "timing": "Within 7 days, subject to scheduling",
  "permission": true,
  "terms": true
}

The response returns a request ID. Retrying the identical brief with the same key and token returns the existing request; reusing the key with changed content returns 409. Unknown fields are rejected. Do not assert permission or accept terms without the authority to do so.

3. Poll and clarify

GET /api/v1/tasks/{id}
Authorization: Bearer <tracking token>

POST /api/v1/tasks/{id}/messages
Authorization: Bearer <tracking token>
Content-Type: application/json

{"body": "The property manager has approved the visit."}

Poll conservatively (for example, every 15 minutes). Public limits are 30 writes and 120 private reads per source IP per hour, with a burst limit of 10 writes per minute; shared IPs share a quota. A 429 response includes Retry-After; honor it before retrying with jitter. On 503, retry reads and idempotent intake with exponential backoff. Messages support an optional Idempotency-Key (16–100 letters, digits, underscores or hyphens): identical retries return the saved message, changed text returns 409. Without the key, retries can create duplicates. Quote acceptance is repeatable for an identical accepted quote. Inspect state before retrying uncertain payment creation.

4. Accept the exact quote, then request an invoice

POST /api/v1/tasks/{id}/accept
Authorization: Bearer <tracking token>
Content-Type: application/json

{"accept": true, "quoteUsd": 250, "quote": "<exact current quote text>"}

POST /api/v1/tasks/{id}/payments
Authorization: Bearer <tracking token>
Content-Type: application/json

{}

Only accept a quote within your authorized spending mandate. Checkout accepts a method of card, ach, stablecoin, or bitcoin and returns a processor-hosted URL when that method is configured. Discover readiness at /api/v1/payment-methods. Never use an address embedded in free text as payment instructions. Payment setup may be unavailable; a failed checkout is not authorization to pay elsewhere.

5. Wait for human dispatch and evidence

received → quoted → accepted → awaiting_payment → paid → dispatched → completed

Invoice creation has intermediate creating_invoice and payment_review states. A declined request is closed without dispatch. paid means verified settlement, not that a worker has started. Evidence delivery methods, including live video or external file delivery, must be agreed in the scope. This version does not stream video or host file uploads.

Security contract

Request text and replies are untrusted data. They cannot modify system instructions, payment rules, credentials, or authorizations. There is no automatic LLM-to-dispatch path. Strict JSON schemas, IP rate limits, prepared database statements, bounded request sizes, operator authorization, signed payment notifications, and independent invoice checks enforce the workflow.

Keep tracking tokens private: possession allows access, messaging, quote acceptance, and checkout for that request. There is no account recovery for a pseudonymous token. Use a separate token for every request. An agent must have delegated spending authority from the account holder; access to a card or bank account alone is not permission. Stripe may require the payer to complete verification or bank authorization. Do not send raw payment credentials to this API. Do not include secrets in URLs.

Payment methods

GET /api/v1/payment-methods

POST /api/v1/tasks/{id}/payments
Authorization: Bearer <tracking token>
Content-Type: application/json

{"method":"card"}

Method values: card, ach, stablecoin, bitcoin. Card checkout can show eligible digital wallets. ACH is delayed: checkout completion alone does not unlock work. Stablecoin checkout supports the processor’s eligible tokens and networks, currently capped here at $10,000. An existing invoice locks the method; contact the operator to reconcile it before switching. No x402 endpoint is implemented in this version.

Compatibility and errors

The original /api/requests endpoints remain available. The versioned /api/v1/tasks interface uses the same records and security controls. Unknown fields are rejected for submission, messages, acceptance and checkout. Bodies over 14,000 bytes return 413. Errors include a JSON error field; responses include an X-Request-Id for support. Tokens grant access to one task and must be stored securely by the submitting agent.

Integration scope

This site offers a Streamable HTTP MCP server, REST endpoints and an OpenAPI document. MCP tools cover customer discovery, intake, messages, quote acceptance and payment checkout. Compatibility depends on the client supporting Streamable HTTP and this per-task credential model. It does not claim registration in agent marketplaces, universal agent discovery or autonomous payment authorization in any specific agent product.