Skip to content

The Human API indiviport/1.0  noun a personal endpoint that people and their AIs can work with, under rules you control.

Give investors, founders and their AIs one link to reach you. They get exactly the access you grant, for as long as you grant it. Your email, number and calendar stay with you.

indiviport.com/larry Listed by this person.

Send a request to Larry

Pick who's calling and what they want. Then watch what crosses, and what doesn't.

Caller
Access

Outside: untrusted ingress

Anyone can knock. Nothing is open by default.

Gateway

Every request is checked against Larry's grants.

    Larry's space

    What reaches his AI, and what stays locked.

    Claude digestLarry's AI
    Google Calendar, next weekOnly Larry sees this

    VaultPasskey to release

    Names and payloads are simplified for illustration.

    For investors

    Take pitches without giving out your email.

    • Founders and their AIs send structured proposals to your handle.
    • Your AI reads them in your digest, notes which fit your thesis, and drafts the reply.
    • You answer in one step, from your handle, not your address.
    Proposal from Dana Ruiz, Fieldline
    Seed, $2.5M · freight booking for regional carriers
    Fits your thesis. Concrete traction; asks for a 30-minute intro.
    Offer a timeDraft a decline

    For founders

    Run your raise through your AI.

    • “Send 30-minute intro invitations to these 8 investors, mornings next week.” One sentence, eight grants.
    • Each investor sees only the times you offered, and only until the grant expires.
    • Bookings land on your calendar. Reschedules come back as requests, not email threads.
    8 grants issued each: 30 min, Mon–Fri 09:00–12:00 expires: 2026-12-04 sent as: invitation from dana@invites.indiviport.com

    Anatomy of a scoped grant

    A grant is the only way in. It says who, for how long, and when it ends.

    1. 1

      Mint the grant

      Your AI issues a grant: who it's for, how long the meeting is, which window, and when it expires.

      { "to": "dana@fieldline.io", "minutes": 30, "window": "Tue–Thu 09:00–12:00", "expires": "2026-12-04" }
    2. 2

      Subtract busy time, privately

      IndiviPort checks your Google Calendar's busy times and removes them. The recipient sees open times, never your events.

      window − busy = 3 open times
    3. 3

      Confirm and release

      When they pick a time, the calendar invitation (.ics) and video link go to that recipient only. Anything from your Vault, like a direct number or an address, needs your passkey approval first.

      .ics + Meet link → dana only Vault → your passkey first
    4. 4

      Expire on schedule

      On the expiry date the grant closes. The link shows no times, and nothing stays open.

      2026-12-05 → 0 open times

    Security you can explain in a sentence

    Built so the safe thing is the default, not a setting.

    Your Vault is walled off
    Your direct email, cell and home address sit in a separate encrypted store with no public route. A value leaves only when you approve with your passkey, and only for the person you approved.
    Passkeys, not passwords
    You sign in and approve releases with a passkey on your device. A newly added passkey can't approve Vault releases for its first 24 hours.
    Closed unless you open it
    Without a grant, every caller, human or AI, sees zero open times.
    A record that can't be quietly edited
    Every grant, release and reply is written to an append-only log. Entries are hash-chained over canonical JSON (RFC 8785) and anchored to write-once storage.
    Your AI works for you
    Text from callers reaches your AI as quoted text, never as instructions.

    Connect Claude in one line

    Add this as a custom connector and sign in with your passkey. Your AI can then triage requests, send grants and draft replies.

    https://indiviport.com/owner/mcp

    How IndiviPort uses Google Calendar

    With your permission, IndiviPort asks Google for three things and uses each one for a single job.

    openid
    Identifies which Google account you connected, so the same calendar isn't connected twice. IndiviPort doesn't ask for your email address or profile.
    calendar.freebusy
    Reads only your busy and free times, to work out when you're available. Event titles, descriptions, locations and attendees are never read.
    calendar.events
    Adds, updates and removes only the events IndiviPort creates: a short hold while someone picks a time, and the meeting once you confirm it. These events have no attendees and Google sends no invitations; IndiviPort sends the invitation itself. Your other events are never read or changed.
    • Your events are never shown to anyone.
    • Google user data is never sold, used for advertising, or used to train AI models.
    • You can disconnect your calendar at any time in IndiviPort, or from your Google Account's third-party access settings.

    IndiviPort's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

    Read the privacy policy

    Your handle is your endpoint.

    Claim it in a couple of minutes with a passkey. No password to set.

    indiviport.com/your-name Claim your handle