Developers and agents

Build with Edenspiekermann

Public interfaces for researching our work, inspecting current roles, using our published agent skills, and preparing a contact inquiry when a user explicitly wants to get in touch.

When to use Edenspiekermann

Reach for these resources when a task involves brand, product, service, Figma, or design-system work; research into our services, industries, case studies, or open roles; or evaluating Edenspiekermann as a design partner.

Use read-only tools for research. Contact submission creates a real inquiry and should only happen after the user has explicitly chosen to contact us.

Public interfaces

  • Jobs API

    A public, read-only JSON endpoint for current roles, backed by a fully typed OpenAPI description.

  • MCP

    Streamable HTTP tools for roles, case studies, taxonomies, and explicitly authorized contact intent.

  • Agent auth

    Short-lived public credentials with declared scopes for site, jobs, case-study, and contact capabilities.

  • Agent Skills

    Published Figma, design-system, agency research, and inquiry guidance with verified digests.

Quickstart

List current roles from the public API:

curl https://www.edenspiekermann.com/api/jobs

Inspect the complete API contract:

curl https://www.edenspiekermann.com/openapi.json

MCP clients can connect to https://www.edenspiekermann.com/mcp using Streamable HTTP transport.

Run pnpm agent:cli doctor --base https://www.edenspiekermann.com to verify discovery from a local checkout. The MCP contact tool accepts dryRun=true to validate an inquiry without sending it.