{"files":{"SKILL.md":"---\nname: emailverify\ndescription: \"EmailVerify API skill. Use when working with EmailVerify for sendCode, checkCode. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# EmailVerify\nAPI version: 1.0.0\n\n## Auth\nBearer bearer\n\n## Base URL\nhttps://ev.apis.paypi.dev\n\n## Setup\n1. Set Authorization header with your Bearer token\n3. POST /sendCode -- create first sendCode\n\n## Endpoints\n\n2 endpoints across 2 groups. See references/api-spec.lap for full details.\n\n### sendCode\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /sendCode | Send verification code |\n\n### checkCode\n| Method | Path | Description |\n|--------|------|-------------|\n| POST | /checkCode | Check verification code |\n\n## Common Questions\n\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Create a sendCode?\" -> POST /sendCode\n- \"Create a checkCode?\" -> POST /checkCode\n- \"How to authenticate?\" -> See Auth section\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Create/update endpoints typically return the created/updated object\n\n## CLI\n\n```bash\n# Update this spec to the latest version\nnpx @lap-platform/lapsh get emailverify -o references/api-spec.lap\n\n# Search for related APIs\nnpx @lap-platform/lapsh search emailverify\n```\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api EmailVerify\n@base https://ev.apis.paypi.dev\n@version 1.0.0\n@auth Bearer bearer\n@endpoints 2\n@toc sendCode(1), checkCode(1)\n\n@group sendCode\n@endpoint POST /sendCode\n@desc Send verification code\n@optional {email: str}\n@returns(200) {success: bool, message: bool} # Success - Email sent\n@errors {400: Invalid or incorrectly formatted email given, 401: Invalid API key}\n@example_request {\"email\":\"test@test.com\"}\n\n@endgroup\n\n@group checkCode\n@endpoint POST /checkCode\n@desc Check verification code\n@optional {email: str=test@test.com, code: str=123456}\n@returns(200) {success: bool, message: str} # If success is true, the user has given the correct code. If not the code is incorrect. \\ Check the message for more information\n@errors {401: #### Invalid API key, 403: #### Tries for this email exceeded.  To prevent abuse and brute forcing, we limit the number of checkCode requests for each email address to 20. \\ This means if more than 20 requests are made you will have to send another code to your user, this will reset the limit.}\n\n@endgroup\n\n@end\n"}}