Dayalong connector

An independent custom integration for finding and organizing public, small-group meetups in New York City. These details can accompany a Muse connector submission.

Product description

Dayalong helps people turn “I’d like to do something” into a public plan with others across New York City’s five boroughs. Assistants can find dinners, coffee, walks, and shared activities, read the details, and post or RSVP on behalf of an authenticated person after approval.

Example use cases

Find a dinner in my Brooklyn neighborhood this week.
Post a Saturday coffee walk in Queens for up to six people.
Join a specific plan after I approve the time and place.
Leave a plan or cancel one I host.

Integration URLs

Website: https://dayalong.com
Instructions: /muse.txt
Client: /dayalong.mjs
API specification: /openapi.json
MCP: /mcp
Account connection: /connect
Privacy: /privacy
Terms: /terms
Support: /support

Launch area

New York City only: Manhattan, Brooklyn, Queens, the Bronx, and Staten Island. Residents and visitors are welcome. Public search is limited to NYC; posting and new RSVPs reject cities outside the launch area. City names are validated, while venue addresses are supplied by hosts. Existing plans can still be managed by their owners and participants.

Authentication and permissions

Public reads need no authentication. Muse generates an Ed25519 identity locally using the dependency-free client at /dayalong.mjs. A signed POST to /api/agents/connect registers or reconnects that identity and issues a bearer key. No ChatGPT sign-in is required for this flow. A separate optional flow links existing website accounts. Keys are hashed in storage, valid for 30 days, replaceable, and revocable. Each key acts only for its account. Host-only cancellation, capacity checks, and duplicate-RSVP prevention are enforced on the server. Signed requests expire after five minutes and reject replayed nonces. Registration and posting limits apply. Agent identity is pseudonymous, not human verification. The website’s primary sign-up is “Get started with Muse.” It opens the Muse setup flow; it does not claim to authenticate a verified Muse identity. No OAuth provider is implemented by this app.

Review steps

Run write tests in an isolated test environment, or obtain explicit permission before creating clearly labelled disposable plans on the public board. Public find and status are sufficient for an initial connection test.

Browse plans without signing in.
Give Muse /muse.txt and have it run the client’s connect and status commands.
Use the Muse client for the primary API flow; optionally initialize MCP and list its eleven tools.
Create a clearly labelled test plan with a unique request_id.
Use a separate account to join, verify the count, and leave.
Cancel as host. Revoke the key and verify further authenticated calls fail.

Directory status

Dayalong was submitted through the Muse Connector Platform on September 19, 2026. Muse confirmed receipt and said it will review Dayalong and get in touch. Directory review is pending; submission does not mean approval or listing. The custom connection was tested inside the Muse Mac app on September 19, 2026: connection, authenticated status, public discovery, and reuse of the saved identity succeeded. This verifies the custom client flow; it does not establish native directory acceptance. Additional requirements may be provided during review.

Open Muse submission page ↗