# Roberson > Likeness rights, cleared. Roberson records a likeness agreement as terms, checks each proposed > use of a person's face, voice or persona against them, routes anything the terms do not settle > to a person, and issues a signed receipt for every approved use. Made by Zelos Inc. Roberson is neutral between the person and the party using the likeness. It is not a marketplace and does not find talent. It never says a use is lawful; it records what was agreed and decided. ## Words - Dossier: the record about one person. - Agreement: terms between the person (or their representative) and a named party, recorded as rules: grants (permissions), exceptions (prohibitions) and obligations (duties). - Source: where an agreement's terms come from: a document (name, clause, excerpt, hash) or terms stated directly in Roberson by the person or their representative, with no document. - Grant: a permission for one likeness type with uses, territories, an end date, channels where the content may appear, content classes it is never for, and an approval mode. - Likeness types: image, voice, persona. - Uses: marketing, de_aging, dubbing, new_dialogue, persona_chat, archival, resale, organic_talent, organic_brand, paid_talent, paid_brand, press, ai_variation, training. - Channels (for uses that place content): instagram, tiktok, youtube, facebook, x, snapchat, pinterest, linkedin, twitch, podcast, radio_audio, brand_website, email, print, retail_ooh, tv_streaming. A request names each channel, never a group. - Content classes a grant may be never-for: beauty, tech, film, music, fashion, food, automotive, travel, general, sports, political, alcohol, tobacco, gambling, crypto, financial_services, pharmaceutical, weapons, military, adult, posthumous. Anything else routes to a person. - Territories: ISO country codes, or WW for worldwide. Worldwide stands alone. - Approval modes: human_review (a person decides every request) or within_grant (a use inside the grant needs no further decision; the record still shows it). - Silence: a grant may leave uses, territories, dates or channels unstated. Silence is recorded as silence and never read as "all" or "forever"; a request touching it goes to a person. - Exclusivity: an agreement may record that no other party gets the person's likeness in named content classes until a date. A party may state its own category. Saving an agreement reports conflicts to the holder by name; a request under another party's exclusivity gets the check "No conflicting exclusivity" routed to a person, naming the category, never the other party. - Open offer: an agreement granted to nobody in particular. Anyone may ask under it; the person decides each request. A brand nobody named can ask from the person's public page. - Request: one declared use, decided once: pending, approved or denied. It may list deliverables (what the deal is made of), each recorded delivered by the requester later. - Receipt: the signed decision, bound to the declaration, the agreement version and the record's standing at the time. Public at https://app.robersonai.com/v/; badge at /api/public/badge/. - Standing: whether the person has confirmed the terms the decision rests on, at decision time and now. ## How a use is checked 1. The agreement is recorded as rules; the person confirms them through a link. 2. A party declares a use: likeness type, uses, channels, territory, duration in days, content classes, production, exact script for a voice use, deliverables if the deal has parts. 3. The evaluator runs deterministic checks against the rules. Each check passes, fails, or routes to review. No model takes part in the decision. 4. A person with recorded decision authority approves or denies, attesting the review checks. 5. The receipt is signed and published. A voice clip can be generated only under a receipt bound to an exact script; the clip's hash goes on the record and it stops playing when the approved window ends or the approval is ended. 6. Deliveries are recorded by the requester as they happen; the request shows complete when all are. A recorded delivery is the requester's word; Roberson does not verify publication. ## For agents - MCP endpoint: https://mcp.robersonai.com/workspace/mcp (Streamable HTTP, OAuth; a person signs in once and picks the workspace the agent acts for). Discovery: https://mcp.robersonai.com/.well-known/mcp.json. Tool guide: https://mcp.robersonai.com/llms.txt. - Tools: get_connection_context, find_rights_subject, search_grants, check_clearance, request_authorization, list_authorization_requests, get_authorization_request, record_delivery, verify_certificate, generate_authorized_clip, get_coverage, get_usage. - A fictional demo with no sign-in: https://mcp.robersonai.com/mcp. ## Pages - https://app.robersonai.com/how-it-works: the product, the demo video, a sample terms page. - https://app.robersonai.com/for-organizations: for business affairs and representatives. - https://app.robersonai.com/verification: each field of a receipt, and what a receipt does not establish. - https://app.robersonai.com/demo: the demo video. - https://app.robersonai.com/v/: a public receipt. Example: https://app.robersonai.com/v/82ab2aae-19f7-4afb-ba79-e68901bcbe35 - https://app.robersonai.com/p/: a person's public page with their published terms. - https://app.robersonai.com/pricing, /terms, /privacy, /support, /about-the-name. ## What a receipt establishes, and what it does not It establishes who approved what, under which agreement version, for which uses, channels, territory and window, and whether the person had confirmed those terms. It does not establish that the use is lawful, that identity was verified beyond the account sign-in and confirmation link, that the underlying contract is enforceable, or that nothing else was agreed elsewhere. Anyone can verify a receipt with the published key; verification does not require trusting Roberson.