# Zartico

> Zartico is a Salt Lake City based destination-intelligence software company, founded in 2019,
> that operates the Zartico Destination Operating System (ZDOS) for destination marketing and
> management organizations, states, airports, attractions and ski resorts. It fuses daily
> geolocation observations, credit-card spending data, lodging and short-term-rental data, event
> demand and DMO digital analytics into one integrated data model.

Generated by API Evangelist on 2026-09-05 from this repository's artifacts. Zartico serves no
llms.txt of its own: https://www.zartico.com/llms.txt returns HTTP 404, as does every other host
on the estate.

## What Zartico publishes for machines

Zartico has NO developer portal, NO REST API reference, NO OpenAPI, NO GraphQL endpoint, NO
webhooks, NO AsyncAPI, NO MCP server, NO agent card and NO published SDK. An agent looking for a
callable Zartico product API will not find one; access to ZDOS is through the browser
application after a sales conversation.

Two machine-readable surfaces do exist and are anonymously readable:

- OGC Web Services (WMS 1.3.0, WFS 2.0.0, WCS 2.0.1):
  https://geoserver.zartico.com/geoserver/ows
  The GetCapabilities documents ARE the contract. 34 WMS layers, 27 WFS feature types across the
  `zartographer` and `regions_app` workspaces - client boundaries, client regions, census tracts,
  county subdivisions, incorporated places, ZCTA and state/county boundaries, points of interest.
  Fees: none. AccessConstraints: none.
- OpenID Connect / OAuth 2.0 discovery (Okta):
  https://login.zartico.com/.well-known/openid-configuration
  https://platform.zartico.com/.well-known/openid-configuration
  Identity metadata for the ZDOS applications. There is no resource-server API behind them that a
  third party can call, and no Zartico-authored scopes - the seven OIDC scopes plus Okta's own
  org-management defaults.

## Contracts in this repository

- openapi/zartico-geoserver-wms-capabilities.xml - WMS 1.3.0 GetCapabilities, fetched verbatim
- openapi/zartico-geoserver-wfs-capabilities.xml - WFS 2.0.0 GetCapabilities, fetched verbatim
- openapi/zartico-geoserver-wcs-capabilities.xml - WCS 2.0.1 GetCapabilities, fetched verbatim
- well-known/zartico-login-openid-configuration.json
- well-known/zartico-login-oauth-authorization-server.json
- well-known/zartico-platform-openid-configuration.json
- well-known/zartico-platform-oauth-authorization-server.json

## Derived artifacts

- conformance/zartico-conformance.yml - OGC, OIDC, OAuth 2.0 conformance with per-entry evidence
- authentication/zartico-authentication.yml - four auth postures across the estate
- scopes/zartico-scopes.yml - 7 OIDC scopes, 0 Zartico-authored
- conventions/zartico-conventions.yml - OGC request/response semantics, reversibility, idempotency
- security/zartico-domain-security.yml - TLS/HSTS/SPF/DMARC/DNSSEC/CAA probe
- packages/zartico-packages.yml - 2 first-party npm packages, 0 API clients
- components/zartico-components.yml - the per-customer attribution pixel
- lifecycle/zartico-lifecycle.yml - no versioning, deprecation or status-page policy published
- plans/zartico-plans-pricing.yml - no public pricing; contact-sales only
- rate-limits/zartico-rate-limits.yml - no published limits
- errors/zartico-problem-types.yml - OGC ows:ExceptionReport, observed

## Human surfaces

- Website: https://www.zartico.com/
- Help Center: https://support.zartico.com/
- Blog: https://www.zartico.com/blog
- Security: https://www.zartico.com/security
- Privacy Promise: https://www.zartico.com/privacy-promise
- Careers: https://www.zartico.com/careers
- Request a demo: https://www.zartico.com/see-a-live-demo
- GitHub organization: https://github.com/zartico (0 public repositories)

## How customers actually integrate

Integration with Zartico is INBOUND, not outbound. A destination grants Zartico read access to
its own systems rather than calling a Zartico API:

- Google Analytics: grant read access to the Zartico account
  https://support.zartico.com/integrate-google-analytics
- Ad server (Google Campaign Manager): add data@zartico.com as a reporting user
  https://support.zartico.com/integrate-your-ad-server
- Website attribution: deploy a per-customer geolocation pixel via Google Tag Manager
  https://support.zartico.com/integrate-zartico-website-attribution

## Provenance

This file was GENERATED by API Evangelist from publicly reachable material. It is not published
by Zartico and does not speak for Zartico. Corrections: https://github.com/api-evangelist/zartico