Skip to content
Machine Outcome
Proof How it works Integrate Work with us Trust boundary
Run locally
Explore MOVNavigation
  • Overview
  • Why MOV
  • Decisions
  • How it works
  • Proof
  • Integrate
  • Trust
  • FAQ
  • Work with us
← Back to MOV

Operator & contact

Contact

One direct route for product, paid-flow, privacy, licensing and security questions.

Machine Outcome VerificationSweden

Operator

Sarmad Tawfeek
Machine Outcome Verification (MOV)
Sweden

Email: sarmad@machineoutcome.com
Personal site: sarmadtawfeek.se
Profiles: LinkedIn · GitHub

Paid Runtime Acceptance work

If you are using a paid API, MCP tool or agent service and want to test MOV on one real flow, email sarmad@machineoutcome.com with the flow or endpoint, what your agent does next, and one requirement that must be true before the result is used. The first scope is intentionally small and no invoice or payment request is created until scope, price, currency, tax handling and contracting details are explicitly agreed.

Security

For vulnerability reports, use sarmad@machineoutcome.com and read the security disclosure guidance.

Privacy & licensing

Privacy requests: sarmad@machineoutcome.com.

Software licensing questions or commercial exceptions: sarmad@machineoutcome.com.

Commercial identity gate: the exact establishment/postal address and organization/VAT identifiers, where applicable, must be added before the first paid commercial engagement is invoiced. MOV will not invent or publish unverified registration details.
Machine Outcome

The acceptance layer between machine payment and machine action.

sarmad@machineoutcome.com

Built and operated by Sarmad Tawfeek · Sweden.

Personal site LinkedIn GitHub

Product

Why MOV Failure proof How it works Try locally One real flow

Concepts & resources

x402 vs acceptance AI agent payments API contracts vs acceptance README llms.txt

Trust & legal

Security License Privacy Terms Contact
© 2026 Machine Outcome Verification Runtime Acceptance · x402-first · Local-first Back to MOV ↑