Skip to content
Market Monolith

Market Monolith API

Program the next
market from the stack
you already run.

Connect your storefront, catalog, ERP, applications, and AI to one market-expansion platform. Create territories, measure local visibility, build Territory Stores, activate digital and physical growth, and bring the evidence back into your software.

Get your API keyExplore the API
An original documentary-style photograph of a field representative having a brief doorstep conversation
Doorstep conversationsPOST /v1/operations {"service":"doorstep"}Planned API · approval required
An original documentary-style photograph of a field installer placing a fictional Territory Store yard sign beside an intersection
Territory Store yard signsPOST /v1/operations {"service":"signage"}Planned API · requirements checked
An original documentary-style photograph with a Territory Store door hanger prominently visible beside a field representative
Territory Store door hangersPOST /v1/operations {"service":"door_hanger"}Planned API · proof returned

Act 1

Connect the stack.

A market-expansion layer
for commerce software.

Get a key. Make a real request.
Keep building.

Every request becomes
something you can follow.

Available now: authenticationPlanned: business execution

Market MonolithDeveloper control plane Authentication
GET /v1/me
{
  "accountRef": "acct_denver",
  "applicationRef": "app_storefront",
  "scopes": ["identity:read"],
  "businessAccess": "not_enabled",
  "billable": false
}
200 OKAuthentication confirmed

Operation topology (planned model)

ApplicationYour integration
TerritoryGeographic scope
QuoteScoped terms
EvidenceProof of activity
ResultOutcome
UsageActivity capture
SettlementFinancial close
Operation ID
op_87f2cb6f
Timestamp
2025-05-22T14:32:09Z
Territory
US-DEN-001
Region
us-west-2
Planned: business execution
An original documentary-style photograph of a local field representative respectfully knocking on a customer's door on behalf of a fictional Territory Store
Illustrative planned actionDenver Metro · doorstep visit

One request · one real-world action

A local operator knocks on behalf of the Territory Store.

Store
TrailPeak · Denver
Service
Doorstep conversation
Control
Approval required
Proof
Arrival + reviewed evidence

Doorstep action preparedNothing dispatches until the approved scope is funded.

This is an illustrative planned business operation. It shows a single approved doorstep action tied to a fictional Territory Store, not a live dispatch.

An original cinematic aerial market with a fictional versioned territory boundary, visibility grid, and evidence locations

Act 2

Understand
the market.

Turn commerce context into a territory your software can measure, compare, and operate.

Market intelligence sequencePlanned API
  1. 01POST /v1/catalog/importsImport the catalog context
  2. 02POST /v1/research-runsRun subject-specific research
  3. 03POST /v1/territoriesCreate a versioned territory
  4. 04POST /v1/local-rank-scan-runsMeasure observed visibility
  5. 05POST /v1/opportunity-analysis-runsModel opportunity with evidence
Outdoor gearProduct demand evidence Trail packsKeyword observation Hiking bootsCompetitor presence Camping tentsCustomer signal
Durable outputsEvidence attached
Normalized assortmentProducts · variants · offers · mediaReusable market context
Cited market briefSources · uncertainty · revisionsResearch evidence
Observed visibilityKeyword · location · device · capture timePosition now
Modeled opportunityAssumptions · comparisons · scenariosEvidence-based potential
Observed rank and modeled opportunity remain separate measures.
An original blue-hour aerial photograph of a fictional mountain market

Act 3

Build the
local presence.

Compile catalog, territory, audience, and offer into a market-specific buying experience.

Territory Store compilerPlanned API
  1. 01POST /v1/territory-storesCreate a draft Store revision
  2. 02territory_refterr_denver
  3. 03assortment_refassortment_outdoor
  4. 04audience_refaudience_front_range
  5. 05offer_refearly-season-essentials
Response201 Store revision prepared
An original desktop and mobile Territory Store concept for a fictional TrailPeak Denver assortment
Illustrative Territory Store preview. It is a prepared concept, not a launched customer Store.
Durable outputsv0.7.3
Store revisionDraft · immutable referencePrepared
Local assortmentProducts · offers · mediaBound
Domain planCandidate only · not purchasedPlanned
PreviewDesktop and mobile reviewReady
Approval requiredReview the frozen revisionLocked

Act 4Activate the marketReady for digital or physical activation after approval.

All business routes and Store artifacts in this section are illustrative planned capabilities. Nothing is launched, purchased, charged, or dispatched.

Act 4

Run the market
in parallel.

One objective. Independently scoped digital, mail, phone, field, and attribution operations.

Planned API
POST
/v1/campaign-drafts
objective
generate_qualified_demand
territory_store_ref
ts_denver_front_range
campaign_name
Spring Builder Appointments
kpi_primary
appointments_booked
kpi_target
240
budget_ceiling
$48,750.00 USD
routes
find · reach · place · activate
approval_mode
human_required
Response201 campaign draft created
An original photograph of qualified audience and lead research

Find

Cited ICP and verified business leads.

Sources · consent · revisions
Planned API
POST /v1/operations/find
Status
Research prepared
An original photograph of localized outreach preparation

Reach

Localized outreach with human handoff.

Email · messaging · managed phone research
Planned API
POST /v1/operations/reach
Status
Sequence prepared
An original photograph of QR mail, door-hanger production, and placement

Place

Turn the approved creative into local presence.

Direct mail · QR · door hangers · signage
Planned API
POST /v1/operations/place
Status
Production locked
An original photograph of an operator preparing a route and approved work packet

Activate

Check capacity and prepare governed field work.

Routes · work packets · proof requirements
Planned API
POST /v1/operations/activate
Status
Dispatch locked
Evidence & attributionPlanned API

GET /v1/campaigns/cmp_5561/evidence

  • Accepted production proof4 / 4 channelsReviewed
  • DeliveredRecipient manifestPending execution
  • PlacedLocation-bound proofPending execution
  • SubmittedField evidencePending review
  • QR visitsDestination revision attachedObserved
  • RepliesConsent-aware responseObserved
  • Store sessionsAttributed, not guaranteed salesObserved
  • CostFrozen to the approved revisionNot authorized
StatusDraft · no execution

Act 5Prove and scale.Measure what mattered. Scale what works.

All business routes, campaign states, operations, evidence and attribution values in this section are illustrative planned capabilities. No outreach, production, provider work, spend, dispatch or result has occurred.

Act 5

One API.
Every account in its place.

Build agency and enterprise software across brands and regions while every account keeps its own applications, scopes, budgets, operations, evidence, usage, and settlement.

Planned APIGET /v1/accounts/{account_ref}/portfolio
Planned APIPOST /v1/account-context-selections

Application credentials never inherit another account’s context. Every request is resolved within the selected account boundary.

Authority matrix
TrailPeak OutdoorAlder & Stone HomeNorthline Foods
Applications435
Territories8610
Workspaces
Playbooks
Budgets
Evidence
Webhooks
TrailPeak Outdoor account contextaccount_ref   trpk_outdoor
ERP Expansion Agentapp_ref   trpk_erp_agent

Scopesidentity:readterritories:writeproposals:writeresults:read

Execution
false
Billing approval
false
Agency Campaign Consoleapp_ref   trpk_campaign_console

Scopesidentity:readterritories:writeproposals:writeresults:read

Execution
false
Billing approval
false
Each application’s credentials are scoped and enforced within this account only.
Portfolio timeline
  1. Denver, COTrailPeak Outdoor

    Research preparedMarket needs, competitors, and opportunity mapped.Illustrative planned state

  2. Austin, TXAlder & Stone Home

    Store revision readyTerritory Store draft with assortment and pricing.Illustrative planned state

  3. Raleigh, NCNorthline Foods

    Quote awaiting reviewQuote assembled for review and approval.Illustrative planned state

  4. Manchester, UKTrailPeak Outdoor

    Evidence availableProof of presence and visibility captured.Illustrative planned state

Every market is independently governed within its account.
Governance by design
  • No cross-account dataData partitions and policies enforce isolation.
  • No shared balancesBudgets, spend, and settlement are account-owned.
  • No inherited approvalApproval authority is explicit and never inherited.
  • Membership recheckRoles are revalidated on every request.
  • Application scopeScopes are least-privilege and time-bound.

Opaque refsAccount, application, and entity refs are opaque by design.

Account-owned evidenceEvidence artifacts live and remain within the account.

Independent settlementInvoices, payments, and credits are never pooled or shared.

All portfolio routes, account states, market states, scopes, evidence, usage, and settlement values in this section are illustrative planned capabilities. No account was accessed and no business work, payment, provider action, or settlement occurred.

An original full-width blue-hour aerial view of a metropolitan territory with simultaneous door-to-door, signage, direct-mail, merchandising, retail-check, event, and storefront activity connected to a visible operation receipt rail

Build the market operation

Give your software
the power to move
the next market.

Create the key. Connect the commerce context. Start building with territories, intelligence, Stores, local services, and evidence.

Get your API key Explore the API Read the quickstart

Email → eight-digit code → API key.
Paid operations remain approval-bound.

POST /v1/market-operationsPlanned API
{
  "territory": "triangle-region",
  "objective": "increase_local_visibility",
  "services": ["store", "search", "direct_mail",
               "field", "proof"],
  "parallel": true
}
202 Acceptedoperation_op_8f3c2a17
  • Door to doorActive route
  • Door hangerProof received
  • Lead researchList generated
  • Yard signPlacement active
  • StorefrontRevision live
  • Local presenceApproved
  • Event tableActivation active
  • QR placementAttributed
  • Retail checkEvidence returned
  • Direct mailIn production
  • Local sales visitActive

The market operation request, regional services, routes, receipts, usage, proof, and settlement states are illustrative planned business capabilities. No work, spend, provider action, dispatch, or settlement has occurred.