For people.
And their agents.

Start with the facts

O1 Circle is a private community for people with O-1A, O-1B, or EB-1 approval, built around connections across art, science, technology, business, and sport. Membership applications are open. Approved petitions can support an application before a move. Applying is free; accepting an invitation does not enroll someone in a paid plan.

Application workflow

1. Prepare with the applicant. Use the current schema for fields and choices. Confirm their details and obtain agreement to the privacy notice. Do not infer consent or invent eligibility.
2. Submit the introduction. Send JSON to POST /api/applications with the applicant’s self-declared O-1 or EB-1 category. Let them know that we’ll ask for private, redacted proof if their introduction is selected. No document is needed at this stage. Save the returned private access code securely.
3. Wait for a proof request. The club owner reviews the introduction first. Read GET /api/membership with the private access code. Only proceed when application.verificationRequestedAt is non-null and application.status is pending. A proof request or conditional acceptance email is not final membership approval. Waitlisted applicants cannot upload.
4. Submit requested proof. After that request, upload the file the applicant supplied to POST /api/membership/proof. Obtain their confirmation that it belongs to them and unnecessary details are redacted. Only PDF, JPEG, and PNG files up to 4 MB are accepted.
5. Wait for the final decision. Read the private application status and relay any review note accurately. Corrected evidence must be supplied and approved by the applicant. The owner manually reviews the evidence before final membership approval and an invitation.

Requested documents can be added at the private eligibility section. Do not attempt an upload before a request; the API returns HTTP 409 when uploads are not available. The browser form at /apply supports the same workflow. The schema and OpenAPI document describe the supported API; do not guess undocumented admin endpoints.

Private access

API clients can send the applicant’s code in the Authorization: Bearer <code> header. Browser access uses a secure HttpOnly cookie. Codes must never appear in URLs, public logs, search indexes, or shared transcripts. Use the returned expiry time. If a response is lost, do not repeatedly submit new applications; use existing private access or contact members@o1circle.com.

A code grants access to one application. Knowing an email address does not grant access. Private documents are available for download only to the club owner; an agent cannot retrieve them through the applicant API.

Permission stays with the person

• Do not fabricate approval documents, claim a pending petition is approved, or assume an approved EB-1 petition means permanent residence.
• Keep the applicant’s name, category, and relevant approval or validity dates visible. Ask them to redact unnecessary identifiers before upload. Never submit a complete petition or import a document from an unapproved URL.
• Do not remove evidence, withdraw an application, or accept a membership invitation without their explicit instruction for that action.
• Do not crawl, index, publish, or reuse private application data. Do not send access codes or documents to unrelated services.

Membership evidence is reviewed by a person. It is not a government database check or certification of current immigration status.