Yokai

Created By
ankorstorea year ago
Simple, modular, and observable Go framework for backend applications.
Overview

What is Yokai?

Yokai is a simple, modular, and observable Go framework designed for building backend applications efficiently.

How to use Yokai?

To use Yokai, you can start by selecting one of the ready-to-use application templates for gRPC, HTTP, MCP, or worker applications, and follow the documentation for setup and configuration.

Key features of Yokai?

  • Modular architecture allowing easy extension with built-in and custom modules.
  • Built-in observability features including logging, tracing, and metrics instrumentation.
  • Dependency injection system to manage application components seamlessly.

Use cases of Yokai?

  1. Developing production-grade backend applications with minimal boilerplate code.
  2. Creating microservices using gRPC or HTTP protocols.
  3. Implementing observability in applications for better monitoring and debugging.

FAQ from Yokai?

  • Is Yokai suitable for large-scale applications?

Yes! Yokai is designed to handle production-grade applications with modularity and observability in mind.

  • What programming language is Yokai built with?

Yokai is built using Go, specifically designed for backend development.

  • How can I contribute to Yokai?

Contributions are welcome! Please follow the guidelines in the repository for contributing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ankorstore
Star
698
Language
Go
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago