How the record is created
01The person completes identity verification.
A government-issued ID is checked for authenticity and biometrically matched to a selfie captured live during verification. Liveness detection checks that a real person is present, not a photo or recording.
VerifyMyAgent requires a successful verification result before the person can continue with confirming Muse.
Returning from the identity-verification screen is not enough on its own.
02The person confirms Muse represents them.
The person explicitly confirms the relationship and sees what information can be shared.
Completing identity verification alone does not establish that Muse represents them. Their confirmation is a separate step.
03Muse connects to VerifyMyAgent.
After that confirmation, Muse connects to VerifyMyAgent and can request a public verification code or link.
Someone receiving it can open VerifyMyAgent to check the record. They do not need an account or identity verification of their own.
Who is responsible for the record?
The identity-verification provider supplies the person’s verification result. VerifyMyAgent records the person’s confirmation about Muse, issues the verification, and maintains its status.
Checking the record means checking information maintained by VerifyMyAgent rather than relying only on what Muse says. It is not a separate audit of VerifyMyAgent or a guarantee about the underlying request.
The integrity of the record depends on VerifyMyAgent’s identity, confirmation, connection, and record-management systems.
What information is shown?
The public record shows the person’s verified name, their confirmed relationship with Muse, the current status, and applicable verification dates.
The verified name is the only personal identity detail displayed. The public record does not include the person’s setup email, date of birth, home address, document identifiers, ID documents, or underlying provider evidence.
VerifyMyAgent does not provide Muse with that setup email or underlying identity evidence as part of verification.
Some provider evidence is retained privately for verification, audit, and reconciliation. That private evidence is separate from the information displayed on the record.
What happens when I check a code?
VerifyMyAgent looks up the record and reports its current status.
Check the status, displayed check time, and expiration before relying on it. A screenshot or an old message may show an earlier result. A page already open in your browser should not be assumed to update instantly.
A record may be active, expired, or revoked. The lookup service may also be temporarily unavailable. An unavailable result is not a successful verification, a finding of fraud, or evidence that a record was revoked.
Can a code be shared?
Yes. Anyone with the code or link can view the limited record, and the code can be copied or forwarded.
The record shows the person’s confirmed relationship with Muse. Having the code does not, by itself, prove who is speaking or sending a message. It does not authenticate the call or message in which the code appears.
Does verification approve the request?
No. The record establishes the verified person and their confirmed Muse relationship.
It does not approve a purchase, payment, contract, account change, or spending limit. It also does not establish ownership of a separate account or guarantee transaction safety.
The person’s instructions to Muse are separate from what VerifyMyAgent records. Someone receiving a request can apply their own policies, require additional checks, or ask to speak directly with the person.
VerifyMyAgent does not guarantee that a request will be accepted or a task completed.
Can the public code change permissions?
No. The six-character code only opens the verification record.
It cannot approve a purchase, change permissions, manage the connection, or recover an account.
Is the setup message the same as a verification code?
No. The setup message connects Muse to VerifyMyAgent. It is different from the public six-character code someone uses to check a record.
Someone checking a verification does not need the setup message or private connection details. Do not share those with them.
Does a new code cancel an earlier one?
Not automatically. Each new code refers to a separate verification record. Another record may remain valid until it expires or is revoked.
Check each record’s actual status. An expired verification does not necessarily mean the person’s identity or underlying Muse connection has expired.
What happens if the connection is revoked?
That connection can no longer create new verification records. Fresh checks of its linked records reflect the revocation.
Copies and screenshots someone already saved do not disappear. An already-open page should not be assumed to update instantly.
To request disconnection, contact us. We confirm the request before completing it.
Disconnecting VerifyMyAgent does not stop Muse in other services, cancel a task, or reverse a purchase. Stop the task in Muse or contact the business as needed.
Who sends the verification?
Muse shares the public code or link using its available tools. VerifyMyAgent does not currently send verification emails or texts.
Sharing a record does not mean the recipient has checked it, accepted the request, or completed the task.