Contact support
Email support@boundry.dev for account, project, domain, delivery, receiving, billing, or integration support. Include the affected project ID, region, and any Boundry message or domain ID. Never send an API key, OAuth token, signing secret, password, or complete sensitive message content.
For a suspected vulnerability, follow the private reporting process on the Security page instead of including exploit details in a general support request.
Claude connector help
Boundry connects to Claude through the production Streamable HTTP MCP endpoint at https://api.au.boundry.dev/mcp. The connection uses OAuth 2.0 and asks you to select the Boundry organisation and Sydney project Claude may access.
- Follow the Claude and MCP setup guide.
- If authorization returns to onboarding, finish creating or selecting an organisation and project, then resume the original authorization.
- If a connected tool is unavailable, reconnect Boundry from Claude’s connector settings and approve the requested project scopes again.
- If the problem remains, send support the approximate time, the selected region, the project ID, and Claude’s visible error message.
Domain and delivery help
Domain verification depends on public DNS. Copy each record name, type, value, and priority exactly as shown in the dashboard. DNS propagation can be uneven, so a record may appear at one resolver before the Sydney verification resolver can see it.
For a message problem, include the Boundry message ID and the expected recipient outcome. An accepted API request confirms that Boundry recorded the message; the message timeline and delivery events show what happened after acceptance.
Service information
Public documentation is available at boundry.dev/docs. The Sydney Region Manifest describes the regional boundary and known exceptions. Our Privacy Policy explains how personal information is handled, including support correspondence.