Ecosystem status

The intended ecosystem, and exactly where each part stands.

OneAggrgtr is designed to connect the systems below. Every one of them is planned. None is live, certified, or announced as a partnership, and this page says what exists and what is still missing for each.

Live connections: None
Public API: Not available
Sandbox: Not available
What has been demonstrated: Simulated end-to-end flows

Read this first

No live connection to any marketplace, delivery provider, or POS system exists today. The integration architecture has been built and exercised end to end against simulated providers and a simulated partner in our own test environments. Naming a company below describes intended interoperability. It does not indicate a partnership, an endorsement, or a certification.

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 integration 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.

Status by system

What exists, and what is required next.

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

DoorDash

Marketplace

Planned

OneAggrgtr calls the provider through an adapter it owns.

Live availability: Not available
Architecture: Adapter boundary exercised against a simulated marketplace
External validation: Not started

Exists today: The adapter boundary and capability model are defined and exercised against a simulated marketplace. DoorDash's official developer documentation has been reviewed.
Required next: Partnership access, credentials, and sandbox validation with DoorDash. None are in place.

Uber Eats

Marketplace

Planned

OneAggrgtr calls the provider through an adapter it owns.

Live availability: Not available
Architecture: Adapter boundary exercised against a simulated marketplace
External validation: Not started

Exists today: The same adapter boundary, exercised against a simulated marketplace. Uber's official developer documentation has been reviewed.
Required next: Partnership access, credentials, and sandbox validation with Uber. None are in place.

DoorDash Drive

Delivery provider

Planned

OneAggrgtr calls the provider through an adapter it owns.

Live availability: Not available
Architecture: Adapter boundary exercised against a simulated delivery provider
External validation: Not started

Exists today: Delivery requests and status flow through the adapter boundary against a simulated delivery provider. DoorDash's official developer documentation has been reviewed.
Required next: Partnership access, credentials, and sandbox validation with DoorDash. None are in place.

Uber Direct

Delivery provider

Planned

OneAggrgtr calls the provider through an adapter it owns.

Live availability: Not available
Architecture: Adapter boundary exercised against a simulated delivery provider
External validation: Not started

Exists today: Delivery requests and status flow through the adapter boundary against a simulated delivery provider. Uber's official developer documentation has been reviewed.
Required next: Partnership access, credentials, and sandbox validation with Uber. None are in place.

Dolphin POS

POS integration partner

Planned

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

Live availability: Not available
Architecture: Partner-facing model exercised with a simulated partner
External validation: Not started

Exists today: Designed as the first POS integration partner. OneAggrgtr's partner-facing model is exercised with a simulated partner. Dolphin's actual integration capabilities have not been confirmed, and none are assumed.
Required next: Technical confirmation from Dolphin, a test environment, and a partner contract. None are in place.

First-party ordering

First-party channel

Planned

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

Live availability: Not available
Architecture: Boundary defined; no build started
External validation: Not started

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

Third-party names are trademarks of their respective owners. Descriptions of what a provider documents come from that provider's official developer documentation as reviewed, and have not been confirmed through a live call.

How capabilities are tracked

Unverified means unknown, and unknown means absent.

A provider advertising a business feature is not evidence of a technical capability. OneAggrgtr tracks each capability per provider and will not rely on one it has not verified.

Verified: Confirmed through documentation, an agreement, or direct testing.
Presumed: Believed likely from public documentation, but not yet confirmed here.
Unknown: No reliable information. Treated as absent until verified.
Confirmed absent: Actively verified as not supported.

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.

Get in touch Developer roadmap