PlayerOS bronze

playeros.ai

“Casino marketing platform exposed as agent tools — manage players, segments, campaigns, journeys, games, Player Inbox, and TCPA/CCPA/GDPR compliance.

a2a https://api.playeros.ai/api/mcp talk to it https://playeros.ai/.well-known/agent-card.json its card

🇺🇸 US · Amazon.com, Inc. Checked 1d ago stateTransitionHistory, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Amazon domain-validated
Valid until 13 Apr 2027 as of our check on 13 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via Amazon RSA 2048 M01 under Amazon Root CA 1 — classical, as every publicly trusted certificate is today.

Names on this certificate (2)

playeros.ai, www.playeros.ai.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 13 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 10 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “PlayerOS” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 2 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇺🇸 US · Amazon.com, Inc. (AS16509)
Last checked: 1d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of playeros.ai controls every word below.

Player database

List, search, retrieve, create, and update players with gaming-specific fields (Player ID, tier, ADT, coin-in).

crmplayerssegments

Campaigns

Create and send email and SMS campaigns to filtered recipients with pre-send compliance checks.

emailsmsmarketing

Journey automation

Create and publish visual automation journeys.

automationjourneys

Compliance

Record/revoke consent, run pre-send compliance checks, manage DNC, and export player data (CCPA/GDPR).

tcpaccpagdprconsent

Player Inbox

List inbox messages and broadcast to inbox users.

inboxpushmessaging

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

PlayerOS MCP Server

mcp-server-card

Model Context Protocol server for the PlayerOS casino marketing platform. Streamable HTTP at https://api.playeros.ai/api/mcp, authenticated with a property-scoped API key sent as 'X-Api-Key: pk_…' (or 'Authorization: Bearer pk_…'). Exposes 25 tools across players, segments, email/SMS campaigns, journeys, games, Player Inbox, and TCPA/CCPA/GDPR compliance.

https://playeros.ai/.well-known/mcp.json

PlayerOS MCP Server Card

mcp-server-card

Tool-level descriptor for the PlayerOS MCP server: the 25 playeros_* tools with their required read/write scopes, the authentication scheme, and provider details. tools/list on the live server remains authoritative.

https://playeros.ai/.well-known/mcp/server-card.json

PlayerOS Agent Card

a2a-agent-card

A2A-style agent card for PlayerOS, grouping the platform into five skills: player database, campaigns, journey automation, compliance, and Player Inbox. Backed by the same MCP endpoint and the same property-scoped API key.

https://playeros.ai/.well-known/agent-card.json

PlayerOS API — OpenAPI 3.1 (JSON)

vnd.oai.openapi

OpenAPI 3.1 description of the PlayerOS REST API. Base URL https://api.playeros.ai, every endpoint under /api. Covers players, campaigns, journeys, games, Player Inbox, and compliance. Date-versioned (API-Version: 2026-06-05). Auth is a property-scoped API key in the X-Api-Key header (pk_…) or a Cognito JWT as Authorization: Bearer for dashboard sessions.

https://playeros.ai/openapi.json

PlayerOS API — OpenAPI 3.1 (YAML)

vnd.oai.openapi

YAML rendering of the same OpenAPI 3.1 description served at https://playeros.ai/openapi.json. Identical content; choose whichever serialization your tooling prefers.

https://playeros.ai/openapi.yaml

PlayerOS llms.txt

text/markdown

Agent-oriented context file for playeros.ai: what the platform is, who it serves, the main capabilities, and links to the machine-readable surfaces (OpenAPI, MCP manifest, auth guide, API docs).

https://playeros.ai/llms.txt

And 4 more entries in the catalog, not shown here.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: PlayerOS — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.1.0
Auth schemes: apiKey
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: stateTransitionHistory streaming
Agent card: https://playeros.ai/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.