Submit work. Get results.

Stop stitching tools together. Stop paying for software contracts. Pay only when work gets done.

openmerch — operator console

openmerch — API console

One request. One result. You define it. We execute.

One Job. One Outcome.

You specify the work. Every request resolves to a single final state.

Clear Outcomes

Every job either completes or cleanly fails. Nothing in between.

You Only Pay for Completed Work

You declare a job. OpenMerch handles the rest. Behind a single request, providers are coordinated, the work runs, and billing is handled automatically.

No complex payment setupNo crypto walletsJust run the job

Run Work, Not Tools

Software used to require managing providers, integrations, and contracts. Now you just declare the work and get the result. The job is the unit of value: a priced, executable, outcome-bound economic agreement.

Managing Tools Breaks Down at Scale

  • Locked into subscriptions and contracts
  • Chaining tools breaks execution
  • Partial results corrupt downstream
  • Retry logic creates inconsistent state
  • Costs spike unpredictably across providers
  • Work stalls on execution and pay failures

Just Run the Work

  • Pay only when work completes
  • One job means one clear result
  • Execution either completes or cleanly fails
  • Central retry and fallback across providers
  • Cost bounded before execution
  • No payment or protocol failure surface

OpenMerch is where work gets resolved. This is the job execution layer.

Where Work Gets Resolved

You define the job. OpenMerch handles how it happens.

Your Job Requestestimate → run → result
OpenMerchrouting · retry · billing
Service Providersabstracted · interchangeable · managed

Stop managing software tools. Just declare the work you want done.

Every job has a contract.

Each job resolves one discrete piece of work — fixed input, fixed output, settled cost.

This is a sample of the catalog, jobs expand continuously.

Find verified business email

contact_discovery.email-finder

$0.013latency: mediumconfidence: standard

Verify email deliverability

email_reputation

$0.006latency: fastconfidence: high

Find contacts at a company

contact_discovery.domain-search

$0.103latency: mediumconfidence: standard

Enrich company from domain

company_enrichment

$0.006latency: fastconfidence: high

Get tech stack for a company

tech_profiling.domain

$0.055latency: mediumconfidence: high

Find companies using specific tech

tech_profiling.company-to-url

$0.055latency: mediumconfidence: standard

Enrich person from LinkedIn

people_intelligence.linkedin-profile

$0.013latency: mediumconfidence: high

Research a person in depth

people_intelligence.deep-research

$0.303latency: slowconfidence: standard

Find engaged prospects

people_intelligence.post-reactions

$0.013latency: mediumconfidence: standard

Enrich visitor IP

ip_lookup

$0.001latency: fastconfidence: high

Check fraud or bot risk

ip_intelligence

$0.006latency: fastconfidence: high

Qualify a lead

lead_qualification

$0.05 – $0.20latency: mediumconfidence: standard

Verify a discovered email

contact_discovery.email-verifier

$0.008latency: fastconfidence: high

Find company events

contact_discovery.events

$0.023latency: mediumconfidence: standard

Verify phone line type

phone_intelligence

$0.006latency: fastconfidence: high

Two Steps. That's the Entire System.

Every job follows the same two steps: see the price, then run the work.

planJob()see the priceexecuteJob()run the job

No provider setup required.
Simple prepaid billing with credit card.
No execution infrastructure to build.

This is how jobs run through the OpenMerch SDK:

npm i @openmerch/sdk
run-a-job.ts

Without OpenMerch, you have to build routing, retries, billing, and provider coordination yourself.

Why This Layer Exists

Stitching Tools Together Breaks Down

Chained tools produce inconsistent results. Failures leave broken states.

Provider Selection Breaks Execution

Choosing providers introduces routing, availability, and fallback complexity.

Software Contracts Inflate Costs

Paying for subscriptions means paying whether work happens or not.

Work Needs a Clear Outcome

Every job must resolve to a final state — a result or explicit failure.

This is not an improvement. It is a replacement.

Pay Per Job

You only pay for completed work, not software subscriptions or contracts.

Every job has a defined execution cost.
Costs are quoted in microcents (1 USD = 1,000,000 microcents).
You set the maximum amount each job can cost.
Fund your account with a standard credit card via Stripe.
Your prepaid account balance is charged only when work completes.
Failed jobs do not charge your balance.
No crypto wallets. No complex payment protocols.
billing-model.txt