Skip to content

Ecosystem status

Who connects to whom, and how far each connection has got.

OneAggrgtr connects out to marketplaces and delivery providers, and POS partners connect in to OneAggrgtr. This page shows each system's stage, what was tested, and what is still missing.

Production connections
None yet
Provider test environments
Uber Eats and Uber Direct
Partner API (v1)
Built; not publicly published
Partner sandbox access
By invitation

Three roles

Who connects to whom matters.

Not every system relates to OneAggrgtr the same way. The direction of the connection shapes the architecture.

External providers

Marketplaces and delivery providers. OneAggrgtr connects to them, through adapters it owns and operates.

Integration partners

POS systems. A partner connects to OneAggrgtr's own API, and through it reaches the providers, without building each provider integration itself.

First-party channels

Business-owned websites and apps. Intended to be an OneAggrgtr-owned channel; not built.

By system

What exists, and what is required next.

Names appear as text only, without logos: no partnership or endorsement is implied.

Uber Direct

Delivery provider

Sandbox-tested

OneAggrgtr calls the provider through an adapter it owns.

Tested in the provider's test environment

  • Delivery quote delivery_quote
  • Create a delivery delivery_create
  • Tracking tracking
  • Cancel a delivery delivery_cancel
Exists today
The Uber Direct adapter is built and has been tested in Uber's test environment for delivery quotes, creating a delivery, tracking it, and cancelling it. Regulated deliveries are refused until identity verification is confirmed.
Required next
Production credentials, certification, and operating procedures. None are in place.
Live availability
Not available

Uber Eats

Marketplace

Sandbox-tested

OneAggrgtr calls the provider through an adapter it owns.

Tested in the provider's test environment

  • Accept or deny an order order_acknowledge
Exists today
The Uber Eats adapter is built and has been tested in Uber's test environment for accepting and denying an order. Receiving orders from Uber Eats is switched off until that path is verified.
Required next
Verified order intake, production credentials, and certification. None are in place.
Live availability
Not available

Dolphin POS

POS integration partner

Simulated

The partner connects to OneAggrgtr's integration API, not the other way round.

Exists today
Designed as the first POS integration partner. OneAggrgtr's partner API (v1) is built and exercised with a simulated partner. Dolphin's actual integration capabilities have not been confirmed, and none are assumed.
Required next
Technical confirmation from Dolphin, completed partner testing, and a partner contract. None are in place.
Live availability
Not available

DoorDash

Marketplace

Waiting on access

OneAggrgtr calls the provider through an adapter it owns.

Exists today
The marketplace role is exercised against a simulated marketplace, and DoorDash's official developer documentation has been reviewed. No DoorDash adapter has been built.
Required next
Developer access, credentials, and sandbox testing with DoorDash. None are in place.
Live availability
Not available

DoorDash Drive

Delivery provider

Waiting on access

OneAggrgtr calls the provider through an adapter it owns.

Exists today
The delivery role is exercised against a simulated delivery provider, and DoorDash's official developer documentation has been reviewed. No DoorDash Drive adapter has been built.
Required next
Developer access, credentials, and sandbox testing with DoorDash. None are in place.
Live availability
Not available

First-party ordering

First-party channel

Designed

Intended to be an OneAggrgtr-owned channel; not built.

Exists today
The channel boundary is defined. No storefront or ordering surface has been built.
Required next
Product design and build. Not started.
Live availability
Not available

No live connection to any marketplace, delivery provider, or POS system exists today. A provider's test environment is not production. Third-party names are trademarks of their respective owners and describe intended interoperability only; no partnership, endorsement, or certification is implied.

Represent a provider, a POS, or a merchant?

If connecting to OneAggrgtr is relevant to you, we would like to understand your integration model and be exact about what each side would need.