Refund request: Supermodel analyze fails and support emails are unreachable

[segu239]

Hi Supermodel team,

I am opening this here because the public email contact addresses I found for Supermodel appear not to work / are unreachable, so I do not have another reliable way to contact support.

I would like to request a refund.

Reason:

• I upgraded my plan expecting Supermodel to work with the CLI and local supermodel --fs-watch workflow.
• The CLI is installed and authenticated correctly.
• The command reaches the server and starts the upload/analysis process, but the analysis consistently fails.
• Because of this, I cannot use the product for the purpose I paid for.
• I tried to contact the company by email, but the emails appear not to exist or do not work.

Technical details:

supermodel version
# supermodel 0.6.16 (1a5900b, 2026-05-12T21:23:23Z)

supermodel status
# Auth: Authenticated
# API base: https://api.supermodeltools.com

supermodel analyze src/app/components/notificaciones

Observed output:

7 files to upload

ts        6
gitignore 1

Your code is analyzed server-side and immediately deleted — zero data retained.
supermodeltools.com/privacy

Error: analyzeArchitectureUsingContext failed
analyzeArchitectureUsingContext failed

I also tried variants such as:

supermodel analyze src/app/components/notificaciones --no-shards --force --output json

and the same failure occurs.

Please process the refund or tell me where I can contact billing/support reliably, since email contact has not worked for me.

[segu239]

Additional clarification: the refund request is also because I was charged twice between May 18 and May 19. This double charge is part of the reason I am requesting the refund, in addition to the CLI/API analysis failures described above and the fact that the support emails appear unreachable.

Please review the billing history for those dates and refund the duplicate/incorrect charge as well.

[brainworkup]

Additional clarification: the refund request is also because I was charged twice between May 18 and May 19. This double charge is part of the reason I am requesting the refund, in addition to the CLI/API analysis failures described above and the fact that the support emails appear unreachable.

Please review the billing history for those dates and refund the duplicate/incorrect charge as well.

[brainworkup]

Same; requesting refund; has not yet worked at all.