# Platinum Bonds: One Application for AI agents

Use https://app.surety.team/api/ai/v1/manifest and https://app.surety.team/api/ai/v1/openapi.json.
No login, API key, customer approval page or separate SSN email step. Include SSNs when you have them. If a required SSN is omitted, the application is saved (not submitted), the applicant is emailed a secure link listing what is missing, and the response is status saved_needs_more with tellUser text.
You fill and submit the SAME One Application used by the human form at https://app.surety.team/.
1. GET /api/ai/v1/bonds for the exact bondType value.
2. GET /api/ai/v1/schema, then POST /api/ai/v1/schema with {"answers":{...}} as facts change to obtain the applicable shared sections. Distinguish the requester/insurance agent from the customer. Optional fields stay optional.
3. Collect supplied facts and applicable SSN/DOB securely. Never put personal data in URLs, invent consent/signatures, or request login credentials.
4. POST /api/ai/v1/applications/preview with {"answers":{...}} if you need the human-form missing-field list. It has no persistence or external effects.
5. When instructed by the user to submit, generate and retain a UUID requestId and POST /api/ai/v1/applications with {"requestId":"<UUID>","answers":{...}}. This fills the existing application and submits through the existing Records/Mia work and operational receipt path.
6. Keep the exact requestId AND original full snapshot for retries after pending/error/timeout. Do not create another request. The API does not provide a public PII read/reveal or edit endpoint. No login or cookie setup is required.
7. Report the returned reference/status truthfully. Received is not a quote, underwriting approval, purchase, signature or issued bond. Our team reviews the request and gets back to the customer.
Optional files accepts original PDF/PNG/JPEG documents as {id,filename,mime,contentBase64,fieldKey?}, 10 MB each and 12 MB total. Originals go through the SAME human upload handler before the SAME file submission. Keep original UUIDs, bytes, filenames and order across retries; changed attachments cannot adopt the original request. Document downstream completion remains pending until its receipt proves otherwise. Never claim unsupplied local files were uploaded or that financial statements/signing/payment were completed by submitting this snapshot.