Taker

Taker is a Riyadh, Saudi Arabia-based restaurant technology company (founded 2018, backed by 500 Global) providing an all-in-one online ordering and restaurant-growth platform used by 1,000+ restaurants. Its product suite spans Taker Channels (branded web/mobile ordering), Taker GO (delivery operations), Taker Flow (operations optimization), Taker Grow (marketing automation), and Taker 360 (a unified dashboard across delivery aggregators). The Taker GO delivery-integration API connects restaurants and delivery service providers (DSPs) with bearer-token auth for order creation, tracking, cancellation, and asynchronous status delivery via webhooks, across published sandbox and production environments.

Taker publishes 1 API on the APIs.io network. Tagged areas include Company, Restaurant Technology, Online Ordering, Food Delivery, and Delivery Integration.

The Taker catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Taker’s developer surface includes documentation, API reference, engineering blog, support, authentication, sandbox, and 13 more developer resources.

🌐 Visit website 📡 Source on GitHub

33.4/100 thin ▬ flat Agent 23/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

1 APIs

Company Restaurant Technology Online Ordering Food DeliveryDelivery IntegrationWebhook Saudi Arabia MENA Restaurant

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 33.4/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 8.9 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.9 / 11

Contract Governance 0.0 / 10

Discoverability 6.2 / 9

Regulatory Posture 2.9 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/taker: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Taker GO Integration API

Delivery-integration API connecting restaurants (Taker GO merchants) and delivery service providers (DSPs). Supports order creation, retrieval, cancellation, DSP re-routing, and...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Taker Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Taker Authentication

http · 1 scheme

SECURITY

Taker Domain Security

no transport/DNS hardening detected

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Webhooks

Lifecycle

DataModel

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: taker
name: Taker
description: Taker is a Riyadh, Saudi Arabia-based restaurant technology company (founded 2018, backed by 500 Global) providing
  an all-in-one online ordering and restaurant-growth platform used by 1,000+ restaurants. Its product suite spans Taker Channels
  (branded web/mobile ordering), Taker GO (delivery operations), Taker Flow (operations optimization), Taker Grow (marketing
  automation), and Taker 360 (a unified dashboard across delivery aggregators). The Taker GO delivery-integration API connects
  restaurants and delivery service providers (DSPs) with bearer-token auth for order creation, tracking, cancellation, and
  asynchronous status delivery via webhooks, across published sandbox and production environments.
url: https://raw.githubusercontent.com/api-evangelist/taker/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Restaurant Technology
- Online Ordering
- Food Delivery
- Delivery Integration
- Webhook
- Saudi Arabia
- MENA
- Restaurant
tags_raw:
- Company
- Restaurant Technology
- Online Ordering
- Food Delivery
- Delivery Integration
- Webhooks
- Saudi Arabia
- MENA
- Restaurant
image: https://taker.io/wp-content/themes/taker-2026/assets/images/logo.svg
apis:
- name: Taker GO Integration API
  description: Delivery-integration API connecting restaurants (Taker GO merchants) and delivery service providers (DSPs).
    Supports order creation, retrieval, cancellation, DSP re-routing, and asynchronous order-status webhooks. Bearer-token
    authentication (TAKERGO_TOKEN for restaurants, DSP_TOKEN for delivery providers); JSON over HTTPS.
  humanURL: https://api.help.taker.io/
  baseURL: https://production.go.taker.io/
  tags:
  - Delivery
  - Order
  - Webhook
  tags_raw:
  - Delivery
  - Orders
  - Webhooks
  properties:
  - type: Documentation
    url: https://api.help.taker.io/
  - type: APIReference
    url: https://api.help.taker.io/
  - type: Authentication
    url: authentication/taker-authentication.yml
  - type: Conventions
    url: conventions/taker-conventions.yml
  - type: ErrorCatalog
    url: errors/taker-error-codes.yml
  - type: Webhooks
    url: asyncapi/taker-webhooks.yml
  - type: Sandbox
    url: sandbox/taker-sandbox.yml
  - type: Lifecycle
    url: lifecycle/taker-lifecycle.yml
  - type: DataModel
    url: data-model/taker-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/taker-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://taker.io
- type: DeveloperPortal
  url: https://api.help.taker.io/
- type: Documentation
  url: https://api.help.taker.io/
- type: APIReference
  url: https://api.help.taker.io/
- type: Blog
  url: https://taker.io/blog
- type: BlogRSS
  url: https://taker.io/blog/feed
- type: Support
  url: https://taker.io/contact
- type: TermsOfService
  url: https://taker.io/terms
- type: PrivacyPolicy
  url: https://taker.io/privacy
- type: Authentication
  url: authentication/taker-authentication.yml
- type: Conventions
  url: conventions/taker-conventions.yml
- type: ErrorCatalog
  url: errors/taker-error-codes.yml
- type: Webhooks
  url: asyncapi/taker-webhooks.yml
- type: Sandbox
  url: sandbox/taker-sandbox.yml
- type: Lifecycle
  url: lifecycle/taker-lifecycle.yml
- type: DataModel
  url: data-model/taker-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/taker-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/taker-llms.txt
- type: DomainSecurity
  url: security/taker-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 11
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/taker"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/taker/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/taker/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.