Add DeviceCheck physical-iPhone Safari flow verification

[davekiss]

Motivation

DeviceCheck lets agents verify a website flow in Safari on a physical iPhone without creating a device-provider account or building an Appium, recording and evidence-retrieval pipeline. The caller supplies a public URL, CSS selectors, actions and assertions; the service returns device identity, assertion results, step screenshots, the original recording and file hashes.

• Service name: DeviceCheck
• Live service URL: https://devicecheck-mpp.dave-baa.workers.dev
• Provider URL: https://devicecheck-mpp.dave-baa.workers.dev/provider
• OpenAPI or API reference URL: https://devicecheck-mpp.dave-baa.workers.dev/openapi.json

Summary

• The service is live and accepts MPP payments.
• This PR adds or updates its entry in schemas/services.ts.
• Listed endpoints, prices, and payment methods match the live service.
• Public documentation and icon URLs are stable and accessible. (No optional icon is specified.)
• pnpm generate:discovery succeeds.
• pnpm check:types passes.
• pnpm build succeeds.

Key design considerations

• Integration: First-party API.
• Provider relationship: I own and operate DeviceCheck (Dave Kiss). AWS Device Farm supplies hardware; DeviceCheck executes the flow and delivers its own evidence report. No AWS credentials or raw sessions are sold, and no provider affiliation or endorsement is claimed.
• Directory fit: DeviceCheck adds physical-iPhone Safari flow verification to the directory. I found no equivalent physical-iPhone flow-verification service in the current registry; existing browser offerings such as Browserbase serve adjacent browser-automation needs. The deployed service has passed hosted physical-device execution, native-video delivery and mainnet payment verification. It runs without an operator's computer, persists idempotent jobs, reconciles teardown and bills only complete evidence. It is available as a bounded beta with the explicit capacity and scope below; I am not claiming broad device coverage or mature production scale.
• Payment methods and intents: tempo.charge, Tempo mainnet (4217), USDC.e, 6 decimals. A completed verification costs 5.00 USDC.e / 5000000 base units. MPP Credits are not advertised as accepted.
• Flow: Submit without payment, poll with the returned private job token, then pay at /result when evidence is ready. The same token grants all artifact downloads after payment. There is no account signup. Submission retries are idempotent.
• Scope: Physical iPhone 16 / iOS 18.6.2 / Safari, one public HTTPS origin, at most 12 supported steps and 120 seconds of test execution. Only authorized synthetic flows. No login, purchases, messages, destructive actions, native apps or arbitrary scripts. Results cover supplied assertions; human review and bug diagnosis are not included.
• Billing and retention: A failed assertion is a completed observation. Infrastructure failures or incomplete evidence are not billed. Payment opens only after teardown and evidence storage. Jobs expire after 48 hours; payment closes 15 minutes earlier.
• Beta capacity: One active job and five initial public jobs, with admission pauses when busy or capacity is exhausted. Provider trial funding is an initial subsidy, guarded by a conservative reserve. No customer traction is claimed. Durable Object alarms execute and reconcile sessions independently of an operator's computer; interrupted work is stopped rather than replayed.

Validation

The hosted mainnet canary entered synthetic text into Selenium's public form, submitted it, verified Received!, and correctly failed a deliberate absent-text assertion. Six screenshots and the native MP4 were downloaded, hash-verified and reviewed; the full recording decoded successfully. The phone session terminated before checkout.

A one-cent internal mainnet checkout successfully unlocked all seven artifacts (transaction). This was an owner-funded test, excluded from customer revenue; public pricing remains $5. Local integration also verified $5 testnet settlement, payment retry, cross-job replay rejection, forged credentials, private downloads, concurrent idempotent submission and no charge for pending work. All 25 unit tests pass.

Reviewed synthetic positive and deliberate-failure sample packets are publicly accessible. These earlier local controls are labeled separately from the hosted acceptance test.

[vercel]

@davekiss is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thanks for submitting a service to the MPP directory!

Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria.

Service submission guide

[github-actions]

🔀 Changed Services

✅ Added

• devicecheck

[github-actions]

Closing this PR. The recommended way to list your service is through MPPScan—it follows the standard MPP discovery format and makes your service immediately discoverable by agents, no PR required.