Namogoo

Namogoo Technologies Ltd. is an Israeli (Herzliya) commerce-technology company founded in 2014, originally known for Customer Journey Hijacking prevention and later for its Digital Journey Continuity and Intent-Based Promotions products for online retailers. The company pivoted to real-time predictive AI for the customer experience, rebranded its product and site to Wandz.ai, and was acquired by French experimentation vendor AB Tasty in November 2025, where the technology now powers AB Tasty AdaptiveCX. Namogoo publishes no public REST API or OpenAPI definition; its integration surface is a JavaScript tag plus first-party mobile SDKs distributed through Maven Central (ai.wandz.android:core-wandz), CocoaPods (NamogooIBPSDK), Swift Package Manager (WandzSDK) and Packagist (Magento 2 modules), activated with an Account ID / client ID issued through the Wandz.ai platform portal.

Namogoo is profiled on the APIs.io network. Tagged areas include Company, E-Commerce, Retail, Personalization, and Customer Experience.

Namogoo’s developer surface includes support, authentication, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

25.9/100 emerging ▬ flat Agent 3/100 human only Heartbeat 14/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company E-Commerce Retail Personalization Customer ExperiencePredictive AIMarketing Mobile SDK Israel

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 25.9/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.0 / 17

Access Clarity 7.4 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 4.7 / 9

Regulatory Posture 5.3 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/namogoo/"><img src="https://apis.io/badge/namogoo/card.svg" alt="Namogoo on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 23.8 — up to +15.2 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/namogoo/apis.yml: open an issue on github.com/api-evangelist/namogoo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Security Posture 4

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

Namogoo Authentication

account-id · 2 schemes

SECURITY

Namogoo Domain Security

TLSv1.3 · DMARC

SECURITY

Namogoo Vulnerability Disclosure

contact published

SECURITY

Namogoo Trust Center

trust center published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

Security

Compliance

Authentication

VulnerabilityDisclosure

VulnerabilityDisclosure

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Acquisition

Acquisition

SecondaryMarket

SecondaryMarket

Source (apis.yml)

aid: namogoo
name: Namogoo
description: Namogoo Technologies Ltd. is an Israeli (Herzliya) commerce-technology company founded in 2014, originally known
  for Customer Journey Hijacking prevention and later for its Digital Journey Continuity and Intent-Based Promotions products
  for online retailers. The company pivoted to real-time predictive AI for the customer experience, rebranded its product
  and site to Wandz.ai, and was acquired by French experimentation vendor AB Tasty in November 2025, where the technology
  now powers AB Tasty AdaptiveCX. Namogoo publishes no public REST API or OpenAPI definition; its integration surface is a
  JavaScript tag plus first-party mobile SDKs distributed through Maven Central (ai.wandz.android:core-wandz), CocoaPods (NamogooIBPSDK),
  Swift Package Manager (WandzSDK) and Packagist (Magento 2 modules), activated with an Account ID / client ID issued through
  the Wandz.ai platform portal.
url: https://raw.githubusercontent.com/api-evangelist/namogoo/refs/heads/main/apis.yml
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
  probe_state: unreadable
  source:
  - authentication
  - security
  - url: https://wandz.ai/
    status: 301
    note: declared website redirects to https://www.abtasty.com/adaptivecx/ — a different registrable domain (wandz.ai ->
      abtasty.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-11-06'
  method: derived
image: https://avatars.githubusercontent.com/u/48321538?v=4
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- E-Commerce
- Retail
- Personalization
- Customer Experience
- Predictive AI
- Marketing
- Mobile SDK
- Israel
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/namogoo-trust-center.yml
- type: DomainSecurity
  url: security/namogoo-domain-security.yml
- type: Website
  url: https://wandz.ai/
- type: GitHubOrganization
  url: https://github.com/namogoo
- type: Login
  url: https://app.wandz.ai/login
- type: Support
  url: https://wandz.ai/contact-us/
- type: PrivacyPolicy
  url: https://wandz.ai/privacy-policy/
- type: TermsOfService
  url: https://wandz.ai/terms-of-use/
- type: Security
  url: https://wandz.ai/security/
- type: Compliance
  url: https://wandz.ai/security/
- type: Acquisition
  url: https://www.abtasty.com/blog/wandzai-acquisition/
- type: SecondaryMarket
  url: https://forgeglobal.com/namogoo_stock/
- type: Packages
  url: packages/namogoo-packages.yml
- type: SDKs
  url: packages/namogoo-packages.yml
- type: WellKnown
  url: well-known/namogoo-well-known.yml
- type: Authentication
  url: authentication/namogoo-authentication.yml
- type: Conformance
  url: conformance/namogoo-conformance.yml
- type: Lifecycle
  url: lifecycle/namogoo-lifecycle.yml
- type: VulnerabilityDisclosure
  url: security/namogoo-vulnerability-disclosure.yml
- type: LLMsTxt
  url: llms/namogoo-llms.txt
x-enrichment:
  date: '2026-08-04'
  status: minimal
  artifacts_added: 9
  pass: local-v1
x-coverage:
  state: unreadable
  reason: pdf-only-docs
  detail: Namogoo ships actively maintained first-party mobile SDKs (Maven Central ai.wandz.android:core-wandz 1.0.49, CocoaPods
    NamogooIBPSDK, SPM WandzSDK), but the only reference for them is a 3.7 MB PDF committed to a GitHub repository — there
    is no web API reference, no OpenAPI on any resolvable Namogoo or Wandz host, and namogoo.com now 301s through wandz.ai
    to AB Tasty AdaptiveCX after the November 2025 acquisition.
  evidence:
  - url: https://github.com/namogoo/wandz-android-sample/raw/main/ReadmeAssets/WandzAndroidSDK.pdf
    status: 200
  - url: https://wandz.ai/openapi.json
    status: 404
  - url: https://wandz.ai/.well-known/agent-card.json
    status: 404
  - url: https://www.namogoo.com/
    status: 301
  checked: '2026-08-04'

Namogoo API — frequently asked questions

How do I authenticate with the Namogoo API?

Namogoo uses bearer-token authentication (account-id · 2 schemes). The details are profiled on APIs.io as Namogoo Authentication.

Is the Namogoo API ready for AI agents?

Namogoo has a Kin Score of 25.9 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

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/namogoo"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.