verify_email
Consume the 6-digit code the founder received and start the research pipeline.
When: after create_application, and ideally after the deck has
been uploaded over plain HTTP (see the curl printed by
create_application). Founder has read the code from their inbox.
Before you call:
CONFIRM you have the right code from the founder (not guessing, not stale). Once this succeeds, research starts and is irreversible.
If deck parsing is still pending, that's fine — research auto-defers and dispatches when the deck resolves. Don't wait, don't re-verify.
Returns: status: researching + whether research was dispatched now
or deferred on the deck.
On error:
wrong code— response includes attempts-remaining. Ask the founder to check their inbox again. If the error says the code is invalidated, callresend_verificationfor a new one.no active code— they never received one, or it expired. Callresend_verification.Already verified — idempotent success; returns current status. Don't retry in a loop.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"applicationId": "<applicationId>",
"code": "<code>"
},
"name": "verify_email"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The 6-digit numeric code from the founder's inbox. | |
| applicationId | Yes | Application id from `create_application`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |