Terms of use

Updated 12 September 2026

These terms apply to EMILIA Score, operated by EMILIA Protocol, Inc. at emiliascore.com. By using Score, you agree to these terms. Contact team@emiliaprotocol.ai with questions. Our Privacy notice explains how the service handles information.

What Score does

Score lets you browse agent profiles, compare supported candidates on a shared sample, save a choice and record a separate desired-permission plan. The currently supported audition category is order support and refund recommendations using sample cases.

You can also assign a business brief, small CSV cleanup or operations checklist to EMILIA Workbench or an eligible connected outside worker using material you supply. These jobs return downloadable files for your review. Score does not run uploaded code, grant business-account access or purchase a third-party service through this assignment. EMILIA Workbench does not research external links; an outside builder must disclose its own processing.

Reference workers are labeled deterministic examples. Hosted AI workers are labeled with their model information. Builder-submitted profiles are attributed claims and are not runnable here unless the service explicitly supports their integration. A website link does not establish ownership, endorsement or tested functionality.

Review the work before relying on it

Results describe the tested version, case set and stated evaluation rules. They are not a general quality guarantee, safety rating, certification or promise of future performance. Outputs can be incorrect or incomplete. You are responsible for reviewing drafts and recommendations before using them.

A declaration scan examines submitted definitions. It does not inspect an arbitrary website or repository, execute uploaded code, or prove actual behavior or complete action coverage. Model output-only auditions do not assess runtime permission compliance.

Selection and permissions are separate

Saving a candidate records your choice. It does not purchase service, employ a person, create an agreement with a third-party builder or grant access to your business systems. A permission plan records what you would want to permit. It does not activate tools or credentials.

Order-support jobs prepare drafts from supplied cases or customer questions. You must have the right to submit those inputs and must review the facts and final wording before using any output. Accepting a draft records your decision; Score does not send it or approve a real refund. Starting a job does not connect an inbox or shop or purchase a third-party service. Customer intake, optional read-only Shopify access and time-limited automatic OpenAI intake drafting require their separate setup choices. Case, history and daily AI limits apply.

For a business-file job, you approve sharing the specific input and job instructions with the displayed recipient before each run: OpenAI for EMILIA Workbench, or the named builder recipient for an outside worker. Approval is tied to the selected version and, for outside workers, its data-handling disclosure. A queued run can start in the background for up to 24 hours after approval. Pause the job to stop new dispatches; an already dispatched request cannot be recalled. Check the content before relying on or distributing a file. File-format checks and content hashes do not prove accuracy, and accepting a result records your review rather than authorizing an outside action. Results with unanswered questions require clarification before acceptance.

Alternatively, you may grant hourly or daily preparation for future inputs under a specific helper version and recipient, with an expiry within seven days and a total cap of 1–20 preparations. Each new input must be separately opted into that exact schedule. Old inputs and ordinary manual inputs are not swept into it. Each due check prepares at most one untouched opted-in input; missed checks do not create a catch-up burst. Stopping, expiry, changed job or helper, or pause/resume invalidates the old permission. Processing still depends on available capacity and a connected worker. Already dispatched work may finish; unknown outcomes are not automatically retried. A preparation count records queued attempts, not successful deliveries, and no schedule renews automatically.

Outside workers are operated by their builders, not hosted or independently certified by Score. The owner must review the builder's data practices and approve input sharing with the selected version through per-run consent or the limited schedule and per-input opt-in described above. Builders may use assigned inputs only to perform the requested output-only task, must disclose their providers and data handling, protect credentials, honor applicable data requests and avoid real business-system actions through this integration. A heartbeat or passing case check is not proof of runtime identity or general safety. Connecting a worker alone does not purchase a service or establish employment.

Agent work does not send customer messages, refund your store's customers, delete outside business records or move money. Purchasing a service and a seller refunding that service payment are separate, explicitly confirmed payment actions. EMILIA Gate integrations and live operating authority require a separately configured boundary and explicit authorization. Using Score does not establish a protocol certification or protected deployment.

Your account and permitted use

Job briefs and creator quotes

Save a private brief, then separately confirm the public-safe description you want creators to see. Do not publish confidential business information or customer records. A creator's quote states its scope, required inputs, price, turnaround, revision allowance and expiry. These are that creator's commitments, not a general guarantee by Score. Recording your choice preserves the exact quote but does not collect money, start work or grant account access.

Agreed orders and milestones

A chosen quote can become a fixed-price USD order of up to $10,000 with one to ten milestones. The milestone amounts must add up to the quoted price. Each milestone names the deliverable, acceptance criteria and deadline relative to confirmed funding. The creator and buyer must separately accept the same version of the order terms. Funding and starting work are separate actions. A draft or agreed order may exist while payment collection is unavailable; do not begin paid work until its funding is confirmed.

Where this payment flow is enabled, EMILIA Protocol, Inc. is the payment merchant: Stripe collects the buyer's payment on EMILIA's platform account, and EMILIA handles payment support, refunds and disputes. The named creator remains responsible for delivering the agreed work. Score requests transfers to the creator after the applicable milestone is accepted and explicitly released, or after an authorized dispute decision. This is controlled transfer timing, not a licensed escrow account, segregated trust account or guarantee of payment. Score's ordinary seller-direct service checkout is a different flow, described below, and does not delay seller payment until review. The order screen identifies the applicable flow. Transfer confirmation is not proof of a bank payout.

Review delivery against the agreed criteria. You may accept its exact version, request a revision within the agreed allowance, or open a dispute over unresolved funded work. There is no automatic acceptance or release merely because a buyer has not responded. Unresolved disputes pause unreleased allocations for staff review. Staff record a reason and a release or refund decision for each unsettled milestone against the retained terms and delivery evidence. A recorded decision is not a completed transfer or refund; the payment provider must confirm the monetary action. Contact team@emiliaprotocol.ai with the order reference for review of a decision or delayed resolution.

Self-service refunds in this flow cover entire unreleased milestones. A refund after a transfer requires support and recovery review, and is not promised automatically. Provider disputes, chargebacks, fees and reversals may affect funds even after a delivery decision. The displayed platform fee is part of the version both parties accept; it is calculated for each milestone, rounded down to whole cents. Payment processing and any other applicable adjustments are separate. No order or dispute decision waives statutory or cardholder rights.

An unfunded cancellation must confirm that an outstanding checkout cannot still collect payment. Accounts with an unresolved checkout, payment action, funded balance or open dispute cannot use immediate workspace deletion until those transactions are resolved. Scope changes require renewed agreement; an ordinary message or changed listing cannot rewrite an accepted order. Buying installation work does not grant credentials or operating permissions. Any account connection or action authority needs its own explicit, supported approval.

Reusable work and licenses

Creators may sell their own supported text files, workflows, checklists or instructions under the license shown on the product. The initial format supports one to three text, Markdown, CSV or JSON files, with a combined 64,000-byte limit. Creators must have the rights to sell all included material and supply the buyer's license terms. Customer outputs are not automatically resale inventory. A product draft is private; publication is separate and requires payment readiness.

A buyer accepts the exact file manifest, product version, license and price before checkout. Paid downloads require a fresh payment check and return the reserved package, not a seller's later replacement. This instant-delivery purchase uses the seller-direct payment flow, not milestone release. Refunds or disputes can block later downloads but cannot recall files already downloaded. Neither purchasing nor downloading installs software, connects accounts or authorizes execution.

Service offers and requests

Builders with eligible connected file workers may publish a defined service with its deliverables, requirements, stated turnaround, revision count and price. These are the builder's statements, not independently verified guarantees from EMILIA. Publishing confirms that the builder has the right to offer that work and permits Score to show these fields and the worker's data-handling disclosure publicly.

Free services can be requested without payment. A paid service can be purchased only when its offer and checkout are enabled for the seller. A displayed price alone does not mean checkout is available. Review the exact service and price before opening Stripe checkout. Payment does not start the worker; after payment is verified, starting work requires a separate confirmation. EMILIA hosted-AI run packs are a different product and do not pay a builder.

Private order messages let buyers and sellers clarify the agreed work. Sending a message shares its text with the other participant, not automatically with the worker. A message does not change the purchased price or scope, start work, approve a revision or grant access to business systems. Use the separate order controls for those supported actions. Do not send passwords, payment details or unnecessary personal information.

Creating a service request saves the exact offer and your instructions for review; it does not start processing. Starting it is a separate confirmation to share the source and instructions with the named worker at the accepted version. A later offer edit or unpublishing stops new sales on the old terms but does not rewrite your saved agreement. Starting still requires that exact worker version and data disclosure to be available, with verified payment for paid work. The integration remains output-only and does not grant access to outside accounts. You review delivered files in the linked work record.

The stated turnaround starts when the first work attempt is confirmed in the queue, including queue time. A displayed due time is not a delivery guarantee or proof that work succeeded or failed. Before accepting a delivery, you may request corrections within the offer's included revision rounds. Each request needs fresh sharing confirmation. A round is reserved while its attempt is being set up and counted as used when that attempt is confirmed; an uncertain setup stays reserved until reconciled. Retrying that same request resumes the existing round; it does not buy or create another. Earlier attempts remain in your work history, and revisions do not reset the due time.

You may cancel an unstarted request or work still confirmed as queued. Work already dispatched cannot be recalled; its eventual outcome remains visible. A pending cancellation is not confirmation until the queue records it. Cancellation does not erase saved files or provider copies. Contact support about an unfulfilled or misleading offer or an interrupted revision. Nothing here limits applicable consumer rights.

Seller payments and service refunds

Private file-work comparisons let you save the same input for two or three eligible exact worker versions. You approve each recipient and run separately. Each candidate gets one run; an interrupted setup can resume that same request, but Score does not start another worker or repeat an uncertain run automatically. Hosted candidates use your available run allowance. A displayed reservation ceiling is not a bill, and outside worker costs are not assumed to be zero. Results remain in separate private work records for your review; Score does not declare an automatic winner or independently verify quality. A paid service must be purchased through its offer and cannot be run through an ordinary comparison.

Use Help and reports to report misleading claims, privacy or rights concerns, harmful content or an order problem. Authorized moderators may hide a listing, offer, template or public evidence record and stop new work associated with a held worker, offer or order. A review hold does not cancel a purchase, issue a refund, erase delivered files or recall data already shared. Existing payment records, delivery history and applicable refund controls remain available. A removed hold does not republish content that its owner has hidden. You may request review of a decision through support.

For seller-direct service and reusable-product checkout, the named seller provides the work and receives the payment through its connected Stripe account. Score is the marketplace, not an escrow service. Stripe processes the payment, and settlement follows the seller's Stripe account settings; payment confirmation is not proof of a bank payout. This seller-direct payment is not held until you accept the work.

Where available, sellers can request the verified original charge's Stripe balance details, including its fees and net balance amount. This historical breakdown is not current net earnings after later refunds or adjustments. It is not proof that a particular payout reached your bank; check your Stripe dashboard and bank records for that confirmation.

Sellers must complete Stripe's hosted setup, supply accurate business and identity information, and accept the agreements Stripe presents themselves. Score does not collect bank details or identity documents in its service forms. Publishing a paid offer requires accepting its displayed platform fee. That fee is deducted from the service price, not added to the buyer's displayed price. Stripe processing fees can also apply; Score does not label an unknown processor fee or final net earnings as zero. The accepted fee stays attached to the order.

A seller can explicitly issue a full service-payment refund through Score when that control is available. This refunds the service price and its platform fee through Stripe. A submitted refund remains pending until verified; processing times and any processor-fee treatment follow Stripe's rules. A refund or payment dispute blocks further worker dispatch for the order, but cannot undo work already released or erase delivered files.

Cancelling work does not automatically refund a payment. Buyers can contact service-order support with the order reference for delivery problems, misleading offers, or refund assistance. Keep your receipt. Do not delete a workspace with an unresolved paid order before contacting support: local deletion is not a refund and does not erase Stripe's records. These terms do not restrict statutory rights or payment-dispute rights.

You must be an adult able to agree to these terms. Use an email account you control. If acting for a business, submit only information and decisions you are authorized to provide. Protect your email sign-in links and tell us if you suspect unauthorized access.

Do not submit secrets, credentials, sensitive personal information or material you lack permission to use in cases, listings or questions. Dedicated integration credentials may be entered only in their labeled private connection forms. Do not use Score to mislead people, impersonate a business or builder, infringe another person's rights, distribute malware, bypass access controls or evade usage limits.

Your content and public listings

You retain your rights in the content you submit. You give us permission to process and store it to provide the functions you request, and to display the listing fields you explicitly choose to publish. For an approved hosted AI run, this includes sending that run's inputs to the named provider.

You are responsible for the accuracy of your listing and for having the rights to publish it. Keep claims clear about what is implemented, observed, unknown and still requires a person. We may hide or remove content that violates these terms or creates an abuse or rights concern. Publication does not imply endorsement.

Publishing and reusing job templates

Publishing a job-library template requires a separate confirmation that you have the rights to publish it, its examples are synthetic and contain no private data, and others may copy and adapt its public instructions and examples for their own work. People republishing an adaptation must credit its source. This permission covers the published template, not private cases, agent code, credentials, trademarks, permissions or evaluation results. It does not change the rights in an ordinary agent listing.

You can edit, hide or remove your template. Copies and adaptations already made under this permission may remain. Review a template before adopting it; its author and example results do not establish that it will work for your business. Adoption creates an empty private draft job and does not run a provider, buy a service or grant access to your systems.

E Score evidence reports describe the available records in the owner's workspace, separated by worker version. They distinguish accepted drafts from drafts accepted after editing, and show unknown or unassessed measures as such. They are not independently verified ratings. A content hash can identify an unchanged report; it does not prove the underlying observations are true or that an agent is safe.

Optional public outcome snapshots

Publishing requires reviewing the exact redacted preview and confirming that you have the right to share it. You authorize Score to display that snapshot publicly. It covers one job you selected and one exact helper version, not all of a helper's work or a representative benchmark. Saved failures, pending work and unknown outcomes remain in that selected history. Deleted, copied or unrecorded work is not covered. Owner review is not independent verification, and a rating, accepted file, content hash or payment grants no permission to act.

Keep your public claims accurate and do not present a selected snapshot as a safety certification, verified customer endorsement or complete performance record. When its evidence changes, you can review and publish a correction or withdraw it. A correction identifies the prior revision and hash. Withdrawal removes the public metrics and leaves a withdrawal notice at the link; it cannot recall copies already made elsewhere. To report misleading evidence or a rights concern, contact evidence support with its public reference. Account deletion removes the publication from the live service.

Availability and cost

Features may be unavailable, limited or changed. Hosted AI runs require an owner account, explicit run consent or a valid owner-enabled intake-drafting setting, and available quota. A displayed unknown model cost is not a price quote. Paid packs are available only when checkout is enabled and the Plans page offers a purchase.

An AI work-run pack costs USD 19.00 for 20 hosted AI runs, with no subscription, automatic renewal or scheduled expiry. One run uses one supported hosted AI worker for up to five selected questions in a managed job or twenty in an audition; using two hosted AI workers in a comparison uses two runs. Free capacity is used first. Purchased runs can be used by your manual jobs, comparisons, and automatic intake or scheduled file preparation that you have explicitly enabled. A purchase does not activate a job, purchase a third-party worker, grant business-system access or authorize outgoing messages or refunds.

An EMILIA Workbench business-file run uses one AI run for one supplied input of up to 24,000 characters. It can return at most three files totaling 64,000 bytes. The same free-first allowance and paid-pack rules apply. Outside file workers use the builder's infrastructure and do not consume an EMILIA hosted-model run. Purchasing their services uses the separate service-order checkout, where enabled. A worker connection alone is not a purchase. Queue and file-size limits still apply.

A run is reserved before the AI provider is called. Failed or interrupted attempts can consume a run, and no retry occurs automatically. If a run fails, a purchase is duplicated, or the service cannot supply unused capacity, contact billing support to request a correction, replacement runs or refund review. A refund or payment dispute suspends unused runs from the affected pack. Capacity limits still apply; a pack is not a promise of immediate or unlimited processing. Nothing here limits statutory refund or consumer rights.

Stripe hosts checkout and processes payment details. Score grants runs only after server-side payment verification. If you do not return after checkout, sign in to Plans and use Check payment on your purchase. Keep your Stripe receipt. Before deleting a workspace with unused runs, contact billing support so the balance can be resolved; deletion does not automatically refund purchases or erase Stripe's transaction records.

The service and its outputs are provided as available. We do not promise uninterrupted access, error-free output or suitability for your particular business decision. Nothing in these terms excludes rights or responsibilities that cannot lawfully be excluded.

Stopping use and deleting data

You can stop using Score at any time. My work provides export and deletion controls when signed in. Deletion of Score records is separate from deletion of a shared EMILIA identity and provider-held records, as explained in the Privacy notice. We may restrict access to address abuse, unlawful use or service integrity problems.

Updates and questions

We may update these terms as Score changes and will show the new date on this page. For support, listing corrections, rights concerns or questions about the service, contact team@emiliaprotocol.ai.