Appsamurai

AppSamurai (legally Apps Medya Teknoloji A.S., engineering org Netvent) is a global, AI-powered mobile app growth platform founded in 2016. It offers user acquisition, retargeting, OEM / on-device app discovery, rewarded user acquisition and monetization across one platform, plus Storyly, its AI-powered in-app content experience product for mobile commerce, and the Interceptd ad fraud detection product. AppSamurai reaches over two billion users across more than 130 countries and works with mobile operators and device manufacturers such as Samsung, Xiaomi, Huawei, Oppo and Lenovo. It publishes two APIs. The Storyly External API covers 18 operations over apps, instances, story groups, stories, audiences and segments, authenticated with a bearer JWT, with a provider-published OpenAPI advertised through an RFC 9727 api-catalog on its docs host. The AppSamurai Campaign Spend API is a single keyed HTTP GET returning campaign spend reporting. AppSamurai also runs a live remote MCP server at mcp.storyly.io serving Storyly Placement SDK knowledge to agents, and ships embeddable Placement widget SDKs for Android, iOS, Web, React Native and Flutter. AppSamurai is ISO 27001 certified for information security. This profile was surfaced as a 500 Global portfolio company and enriched by the API Evangelist pipeline.

Appsamurai publishes 7 API contracts indexed on the APIs.io network, including Campaign Spend API, App API, Audience API, and 4 more. Tagged areas include Company, Mobile, Advertising, User Acquisition, and Marketing.

The Appsamurai catalog on APIs.io includes 1 Spectral governance ruleset.

Appsamurai’s developer surface includes documentation, support, engineering blog, signup flow, authentication, API reference, changelog, and 30 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

60.2/100 strong ▬ flat Agent 32/100 agent ready Front door AI 1/6 silent Heartbeat 89/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

3 published contracts 4 Agent Skills

Company Mobile Advertising User Acquisition MarketingApp GrowthAttribution Analytics Mobile Marketing SDKStorylyContent ExperienceIn-App StoriesMCP Mobile Commerce

Kin Score

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

Composite quality — 60.2/100 · strong

Contract Quality 9.2 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 11.8 / 15

Operational Transparency 4.4 / 10

Contract Governance 2.9 / 9

Discoverability 5.9 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 32/100 · agent ready

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

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/appsamurai/"><img src="https://apis.io/badge/appsamurai/card.svg" alt="Appsamurai 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):

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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 49.1 — up to +12.7 composite points
Contract Governance scores 31.8 — up to +8.2 composite points
Operational Transparency scores 44.7 — up to +7.2 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/appsamurai/apis.yml: open an issue on github.com/api-evangelist/appsamurai 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)	standard	36.4	-	1

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.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 7

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

Appsamurai Campaign Spend API

The Campaign Spend API from Appsamurai — 1 operation(s) for campaign spend.

Appsamurai App API

App management endpoints

Appsamurai Audience API

Audience management endpoints

Appsamurai Instance API

Instance management endpoints

Appsamurai Segment API

Segment management endpoints

Appsamurai Story API

Story management endpoints

Appsamurai Story Group API

Story group management endpoints

Scroll for all 7

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

AppSamurai Campaign Spend API

OPEN COLLECTION

Storyly External API

OPEN COLLECTION

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

appsamurai-publish-a-story

AGENT SKILL

appsamurai-pull-campaign-spend

AGENT SKILL

appsamurai-report-on-content-performance

AGENT SKILL

appsamurai-target-content-with-audiences

AGENT SKILL

Appsamurai API pricing

Prices published by Appsamurai, read 2026-10-28 from www.storyly.io/pricing.

Plan	Price
Core Engagement Suite	Starts from $600/m Includes: One Placement Only, Banners & Stories, Basic Interactive Stickers, Basic Analytics, 5 Team Members
Personalization & Widget Suite	Starts from $1000/m Includes: All starter features, plus: Multi-Placement (Up to 3), Smart Flows, All Interactive Stickers, All Wi
Comprehensive Orchestration Suite	Let's Talk Includes: All pro features, plus: Unlimited Placements, Unlimited Flow Requests, Advanced Personalization, Thi

Plan details, limits and sources →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Appsamurai Plans Pricing

3 plans

PLANS

Appsamurai Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Appsamurai Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Appsamurai

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Appsamurai Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Appsamurai API Rules

62 rules · 54 errors 2 warnings 6 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Appsamurai Campaign Spend Overlay

2 actions · update · appsamurai-campaign-spend-openapi.yml

DERIVED

Appsamurai Storyly External Api Overlay

9 actions · documentation

DERIVED

Security Posture 3

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

Appsamurai Authentication

http-bearer/apiKey · 2 schemes

SECURITY

Appsamurai Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Appsamurai Vulnerability Disclosure

Hackerone

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Conformance

Lifecycle

DataModel

Components

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

ToolCrosswalk

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Compliance

Compliance

Authentication

Authentication

Operate 5

Status, limits, changes, and where to get help

HelpCenter

Support

StatusPage

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

PrivacyPolicy

TermsOfService

Plans

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: appsamurai
name: Appsamurai
description: AppSamurai (legally Apps Medya Teknoloji A.S., engineering org Netvent) is a global, AI-powered mobile app growth
  platform founded in 2016. It offers user acquisition, retargeting, OEM / on-device app discovery, rewarded user acquisition
  and monetization across one platform, plus Storyly, its AI-powered in-app content experience product for mobile commerce,
  and the Interceptd ad fraud detection product. AppSamurai reaches over two billion users across more than 130 countries
  and works with mobile operators and device manufacturers such as Samsung, Xiaomi, Huawei, Oppo and Lenovo. It publishes
  two APIs. The Storyly External API covers 18 operations over apps, instances, story groups, stories, audiences and segments,
  authenticated with a bearer JWT, with a provider-published OpenAPI advertised through an RFC 9727 api-catalog on its docs
  host. The AppSamurai Campaign Spend API is a single keyed HTTP GET returning campaign spend reporting. AppSamurai also runs
  a live remote MCP server at mcp.storyly.io serving Storyly Placement SDK knowledge to agents, and ships embeddable Placement
  widget SDKs for Android, iOS, Web, React Native and Flutter. AppSamurai is ISO 27001 certified for information security.
  This profile was surfaced as a 500 Global portfolio company and enriched by the API Evangelist pipeline.
url: https://raw.githubusercontent.com/api-evangelist/appsamurai/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: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
image: https://appsamurai.com/og-default.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-19
tags:
- Company
- Mobile
- Advertising
- User Acquisition
- Marketing
- App Growth
- Attribution
- Analytics
- Mobile Marketing
- SDK
- Storyly
- Content Experience
- In-App Stories
- MCP
- Mobile Commerce
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: appsamurai:appsamurai-campaign-spend-api
  name: Appsamurai Campaign Spend API
  description: The Campaign Spend API from Appsamurai — 1 operation(s) for campaign spend.
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - Campaign Spend
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-campaign-spend-api-openapi.yml
  - type: Documentation
    url: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
- aid: appsamurai:appsamurai-app-api
  name: Appsamurai App API
  description: App management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - App
  tags_raw:
  - app
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-app-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
- aid: appsamurai:appsamurai-audience-api
  name: Appsamurai Audience API
  description: Audience management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - Audiences
  tags_raw:
  - audience
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-audience-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
- aid: appsamurai:appsamurai-instance-api
  name: Appsamurai Instance API
  description: Instance management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - Instance
  tags_raw:
  - instance
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-instance-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
- aid: appsamurai:appsamurai-segment-api
  name: Appsamurai Segment API
  description: Segment management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - Segment
  tags_raw:
  - segment
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-segment-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
- aid: appsamurai:appsamurai-story-api
  name: Appsamurai Story API
  description: Story management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - Story
  tags_raw:
  - story
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-story-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
- aid: appsamurai:appsamurai-story-group-api
  name: Appsamurai Story Group API
  description: Story group management endpoints
  humanURL: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
  baseURL: http://api.appsamurai.com
  tags:
  - story-group
  properties:
  - type: OpenAPI
    url: openapi/appsamurai-story-group-api-openapi.yml
  - type: Documentation
    url: https://docs.storyly.io/docs
  - type: APIReference
    url: https://docs.storyly.io/reference
  - type: GettingStarted
    url: https://docs.storyly.io/docs/introduction
  - type: Authentication
    url: authentication/appsamurai-authentication.yml
  - type: ErrorCatalog
    url: errors/appsamurai-problem-types.yml
  - type: DataModel
    url: data-model/appsamurai-data-model.yml
  - type: Conventions
    url: conventions/appsamurai-conventions.yml
  - type: RateLimits
    url: rate-limits/appsamurai-rate-limits.yml
  - type: LLMsTxt
    url: llms/appsamurai-storyly-llms.txt
common:
- type: Overlay
  url: overlays/appsamurai-storyly-external-api-overlay.yaml
- type: Overlay
  url: overlays/appsamurai-campaign-spend-overlay.yaml
- type: DomainSecurity
  url: security/appsamurai-domain-security.yml
- type: Website
  url: https://appsamurai.com
- type: DeveloperPortal
  url: https://docs.storyly.io/
- type: Documentation
  url: https://docs.storyly.io/docs
- type: HelpCenter
  url: https://appsamurai.com/help/
- type: Support
  url: https://appsamurai.com/contact-us/
- type: Blog
  url: https://appsamurai.com/blog/
- type: GitHubOrganization
  url: https://github.com/Netvent
- type: SignUp
  url: https://dashboard.appsamurai.com/login
- type: Login
  url: https://dashboard.appsamurai.com/login
- type: PrivacyPolicy
  url: https://appsamurai.com/privacy-policy/
- type: TermsOfService
  url: https://appsamurai.com/terms-of-use/
- type: Compliance
  url: https://appsamurai.com/information-security-policy/
- type: Authentication
  url: authentication/appsamurai-authentication.yml
- type: LLMsTxt
  url: llms/appsamurai-llms.txt
- type: Packages
  url: packages/appsamurai-packages.yml
- type: SDKs
  url: packages/appsamurai-packages.yml
- type: WellKnown
  url: well-known/appsamurai-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/appsamurai-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: ErrorCatalog
  url: errors/appsamurai-problem-types.yml
- type: Conventions
  url: conventions/appsamurai-conventions.yml
- type: Conformance
  url: conformance/appsamurai-conformance.yml
- type: APIReference
  url: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
- type: StatusPage
  url: https://status.storyly.io/
- type: Lifecycle
  url: lifecycle/appsamurai-lifecycle.yml
- type: ToolCrosswalk
  url: mcp/appsamurai-tool-crosswalk.yml
- type: DataModel
  url: data-model/appsamurai-data-model.yml
- type: Components
  url: components/appsamurai-components.yml
- type: ChangeLog
  url: changelog/appsamurai-changelog.yml
- type: Plans
  url: plans/appsamurai-plans-pricing.yml
- type: RateLimits
  url: rate-limits/appsamurai-rate-limits.yml
- type: Pricing
  url: https://www.storyly.io/pricing
- type: GettingStarted
  url: https://docs.storyly.io/docs/introduction
- type: LLMsTxt
  url: llms/appsamurai-storyly-llms.txt
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 17
  pass: local-v1
  note: 'Round 2 found the Storyly surface that round 1 missed entirely - a provider-published OpenAPI (18 ops) reached through
    an RFC 9727 api-catalog, a live anonymous MCP server, and a real llms.txt. Also corrected two false positives: the WellKnown/security.txt
    credit was Intercom''s vendor document, not App Samurai''s.'
x-merged-from:
- app-samurai

Appsamurai API — frequently asked questions

Does Appsamurai have an API?

Yes. APIs.io lists 7 APIs from Appsamurai, including Appsamurai Campaign Spend API, Appsamurai App API and Appsamurai Audience API, and 4 more.

Is there an OpenAPI specification for the Appsamurai API?

Yes. APIs.io indexes 7 OpenAPI specifications for Appsamurai, each linked for download from this page.

How do I authenticate with the Appsamurai API?

Appsamurai uses bearer-token authentication (http-bearer/apiKey · 2 schemes). The details are profiled on APIs.io as Appsamurai Authentication.

How much does the Appsamurai API cost?

Appsamurai publishes its prices; its Core Engagement Suite plan is Starts from $600/m as of 2026-10-28. APIs.io lists 3 pricing plans for Appsamurai, with each plan's price, limits and inclusions under Pricing on this page.

Is the Appsamurai API ready for AI agents?

Appsamurai has a Kin Score of 60.2 out of 100 (strong) and an Agent Readiness score of 31.8 (agent-ready), 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/appsamurai"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/appsamurai/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.