DEV Community

Roberto Francisco junior
Roberto Francisco junior

Posted on

I built Messora and need 10 developers to break the onboarding

I spent the last few months building Messora, and I have reached the part that interests me most: letting people outside the project try to break it.

## The problem

Sending raw HTML to an LLM wastes context on markup, navigation, scripts, and layout elements.

In one of my tests, a 62 KB HTML page consumed approximately 21.4k tokens with the tokenizer I was using. After extracting the relevant content as clean Markdown, it used 1,284 tokens.

That was roughly 16 times less context spent reading the same page.

Messora receives a public URL and returns:

  • clean Markdown;
  • structured JSON using a schema;
  • raw HTML when needed.

## Try it without creating an account

The homepage has a public playground:

  1. Open messora.dev.
  2. Scroll to “Teste agora, sem cadastro”.
  3. Enter a public URL.
  4. Click “Extrair dados”.
  5. Inspect the Markdown, JSON, or raw output.

The screenshot above shows the request prepared for https://example.com.

In this recorded execution, the request returned HTTP 200 in 510 ms. This is one observed run, not a performance benchmark.

The public playground uses a separate anonymous demo allowance. It does not represent the balance of a registered beta account.

## API example

   curl -X POST https://api.messora.dev/scrape \                                                                                                                                              
     -H "X-API-Key: YOUR_API_KEY" \                                                                                                                                                           
     -H "Content-Type: application/json" \                                                                                                                                                    
     -d '{"url":"https://example.com","formats":["markdown"]}'                                                                                                                                
Enter fullscreen mode Exit fullscreen mode

A successful page costs one credit. Failed extraction attempts do not consume the credit.

## What I need help testing

I am looking for 10 developers to go through this flow while trying to break it:

Create account → generate API key → make the first successful API request

I already know where every button is. You do not.

I would like to learn:

  1. Where did you get stuck?
  2. How long did it take to receive the first HTTP 200 response?
  3. Which error could you provoke?
  4. Did the error message explain what to do next?
  5. Was the credit cost clear before the first request?

Please try malformed URLs, invalid schemas, blocked domains, and requests without an API key. Only test URLs you own or are authorized to access.

## Current limitations

  • LinkedIn and Instagram are explicitly refused.
  • Targets with heavy anti-bot protection may be limited or refused during the beta.
  • There is no official SDK yet; the API is REST.
  • The beta is free and does not require a credit card.

If you abandon the signup halfway through, that is useful feedback too.

Please do not share API keys in the comments.

After the first 10 tests, I will update this post with the main friction points and the changes made.

Test it: https://messora.dev

Top comments (1)

Collapse
 
messora profile image
Roberto Francisco junior

If you test the onboarding, a short report in this format would help:

  • Where did you stop or hesitate?
  • Time to the first HTTP 200:
  • Error you managed to trigger:
  • Was the error message actionable?
  • Was the credit cost clear?

Please do not share API keys, private URLs, passwords, or personal data.

I’ll summarize the findings and update the post after the first 10 tests. Thanks!