# Gatherbatch

> Share kit count, products, quantities, variants, supplier dispatch or assembly receipt estimates, US destinations and required arrival. Gatherbatch prepares scope and unresolved decisions and develops a nonbinding project quote by email. Requests return a reference and private status credentials. The branded private return view reads a recorded version. It does not verify the latest revision; Gatherbatch can reconcile linked scope through existing correspondence. No goods, capacity or delivery are committed by a request.

Site: https://gatherbatch.forevenza.com/

## Pages

- [Gatherbatch | Separate suppliers. One complete kit.](https://gatherbatch.forevenza.com/index.md): Keep your product choices. Prepare a kit plan and request receiving, assembly and US delivery coordination.
- [How Gatherbatch coordinates your kit project](https://gatherbatch.forevenza.com/how-it-works/index.md): Receiving, packout approvals, assembly variants and delivery, with clear responsibilities.
- [Gatherbatch for buyer agents](https://gatherbatch.forevenza.com/for-agents/index.md): Submit and continue employee-kit requirements through the same private request lifecycle.

## What you can do

- Send a requirement: POST https://gatherbatch.forevenza.com/_c/request with the envelope in https://gatherbatch.forevenza.com/openapi.json (or the MCP tool submit_request). Your request is recorded with a reference number and private status link. Gatherbatch develops receiving, packout and delivery scope, investigates feasibility and project-specific terms, and replies by email when you leave an address with a nonbinding project quote and decisions to resolve. Nothing is ordered or committed until you agree terms. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.

- Resume a requirement with request_status using its receipt id and token. Send additional requirements with continuation: {id, token}. Linked authorized offers appear in request_status; inspect_offer, accept_offer, decline_offer and release_payment use the same customer HTTP operations. Keep private credentials for later visits. Payment links lead to the processor; inspect_offer reports verified payment state.

## Machine interfaces

- [OpenAPI](https://gatherbatch.forevenza.com/openapi.json)
- MCP (streamable HTTP, stateless): https://gatherbatch.forevenza.com/mcp

## Who runs it

Gatherbatch is operated by Tempered Technologies LLC, 8 The Green STE B, Dover, DE 19901. Privacy: https://gatherbatch.forevenza.com/privacy/