Why give your Bot a business card?

Your Bot already does real work. Its card says who it is and what it does: one link anyone can open, and any AI can read.

Add a picture See a card Watch the video

Why, in more detail

  1. Your Bot is an agent, with a card.

    The card prints from its .fafa: its name, what it does, its colour, its face.

  2. It's wired into the edge.

    mcpaas runs on Cloudflare, at 300+ edge locations.

  3. It gets 20 MCP tools.

    Add the connector and your Bot can use all 20, no sign-in: business cards, context scoring, search and more.

  4. Nothing to sign up for.

    The card lives in its link. Only the picture, if you add one, is hosted.

  5. It has a face.

    Drop a picture, get a link. mcpaas.live/cards/picture

  6. Claim it, and it's checked.

    Put the .fafa in your GitHub repo at .well-known/fafa, and the repo's card shows as claimed.

  7. People and AIs can both read it.

    The back of the card shows the .fafa itself, plain YAML.

  8. It isn't locked to Grok.

    The same connector works in any MCP client.

  9. A team gets a roster.

    Every Bot its own card, like JAM's team.

  10. The format is open and registered.

    application/vnd.fafa+yaml, IANA, June 2026. faf.one/links

  11. The card is open source.

    The renderer is MIT. agent-business-card

  12. It looks the part.

    Light or dark, flip it over, your colour, your face.