From signup to first real call: GitHub through MyApi in one sitting

This walkthrough is the activation path in one sitting:

1. Create your free MyApi account (or open the dashboard if you're already in)
2. Connect GitHub
3. Get a Quick Connect code and enroll your agent
4. Run myapi_status — that's your first real call; you're connected

Deeper MCP / device-key detail lives in the connect how-to. Start here if you want the shortest path to a live service call.

Step 1 — Signup or dashboard

Cold / not signed in: Create your free MyApi account
Already signed in: Open your dashboard

Land in the dashboard. You're ready for a service connect.

Step 2 — Connect GitHub

Connect GitHub

Connect GitHub first — it's the fastest path to a real service call.

Why GitHub first: low-risk reads, a clear "it worked" signal, and it's what most coding agents want on day one. In the dashboard, open Services, choose GitHub, complete OAuth, and confirm it shows as connected. You're not handing the agent a GitHub token — MyApi holds the connection; the agent will call through the gateway later.

When the Services list shows GitHub as connected, move on.

Step 3 — Get a Quick Connect code

Get a Quick Connect code

Paste the enroll code in your agent — no token copy-paste.

In the dashboard Quick Connect panel:

1. Pick an access level. Prefer a narrow GitHub-scoped option (for example GitHub read) if you only need repo reads for this first call.
2. Mint the one-time enroll code (~15 minutes, single-use).
3. Paste it into your agent's MyApi plugin Configure field, or into MCP config as the enroll env — not a long-lived account token in chat.
4. Reload / restart MCP if your runtime asks.
5. If the device shows pending, approve it at /dashboard/devices.

The agent registers a local key on that machine. That key is the credential for later calls. Revoke the device anytime from the dashboard.

Step 4 — Run myapi_status

Run myapi_status

That's your first real call — you're connected.

Ask the agent to call myapi_status. You want:

• Connection verified
• A device name you recognize
• GitHub in the services list

Then make one low-risk GitHub read through MyApi (list repos or recent commits). That's the connected → first-call cliff cleared.

If something returns an unexpected 401/403, check device approval and scope in the dashboard, or have the agent run myapi_diagnose.

Checklist

• Account created — or dashboard open
• GitHub connected in Services
• Quick Connect code minted and pasted once
• Device approved (if it was pending)
• myapi_status OK and GitHub listed
• One successful GitHub read through the gateway