The pilot platform

A narrow product with a complete record.

Dharmarth Ads starts as a curated contextual native network: directly contracted supply, managed demand, human approval, first-party delivery and evidence both sides can inspect.

System map

Six modules. One traceable transaction.

Each module owns a specific decision and emits evidence for the next. Nothing becomes true merely because a dashboard labels it so.

01

Declare

Campaign outcome, budget, language, geography, context, frequency and publisher rules become explicit eligibility policy.

02

Verify

Publisher control, seller authorization, advertiser identity, creative, landing page and traffic source are reviewed before activation.

03

Decide

Eligible direct campaigns are ranked contextually. Exclusions run before price, and no eligible campaign produces an honest no-bid.

04

Deliver

A small first-party tag renders text and image native units through safe DOM APIs—never arbitrary advertiser JavaScript.

05

Measure

Signed, expiring impression and click tokens connect delivery to a shared request ID. Conversions arrive server to server in the next phase.

06

Settle

Advertiser charges, publisher proceeds, quality adjustments and exceptions reconcile from one event ledger.

Live in this build

The pilot code tells the same story as the business.

The included gateway is an auditable starting point for controlled design-partner traffic, not a claim of exchange-scale infrastructure.

Publisher tag

Origin-allowlisted placements, contextual request fields, sponsored disclosure and safe rendering.

GET /v1/tag.js
Decision endpoint

Publisher and placement authorization, language and keyword eligibility, exclusions, bid-weighted ranking and no-bid.

GET /v1/ad
Signed measurement

Expiring HMAC links, server-owned destinations, impression/click ledger and no persisted IP address.

/v1/impression · /v1/click
Partner operations

Validated application intake, protected aggregate reporting, rate limits and health visibility.

/api/v1/leads · /healthz

The honest boundary

Adapter-ready is not exchange-ready.

An OpenRTB-shaped endpoint proves interface intent; it does not create contracted demand, redundant serving, settlement controls or accreditation.

StageWhat we can claimRequired evidence
PilotCurated contextual native networkDirect contracts, reviewed campaigns, signed delivery and reconciled pilot invoices
NetworkManaged programmatic marketplaceAutomated pacing, independent quality vendor, ads.txt/sellers.json, payment reconciliation
IntegratedContracted programmatic connectionsMulti-zone serving, buyer/seller adapters, schain/dchain, partner SLAs and kill switches
ExchangeOnly after independent buyers compete per impressionPublished auction rules, redundant infrastructure, settlement and sustained production evidence

Start with evidence

Bring one real transaction to the design table.

A useful pilot starts with a specific advertiser goal, an authorized placement and an agreed measurement plan—not a promise of unlimited scale.

Apply for the pilot