Okuta Omeiza
Okuta Omeiza's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @omeiza-workspace appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the api-mock-services corpus
omeiza-workspace/api-mock-services: Stand-ins for the outside world: the payment gateways, the email provider, the accounting service, the DNS provider, the messaging and the…
- Look up how api-mock-services implements fintech, offline, payments, with answers cited to file and line.
- Reuse a worked example: the commit “Segment, Mixpanel, Amplitude, RudderStack analytics mocks + tes…” (9 files · JavaScript).
- Answer from api-mock-services's real JavaScript source instead of memory (API design and specification).
- How does api-mock-services implement fintech?
- What does specs do in api-mock-services?
Search the GitHub repository omeiza-workspace/api-mock-services with XERJ (https://hub.xerj.org/corpus/omeiza-workspace--api-mock-services). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/omeiza-workspace/api-mock-services api-mock-services && git -C api-mock-services checkout 42e15576d42aeae69efc119132fa672eb5b75c80 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./api-mock-services --url http://127.0.0.1:9200 --prefix api-mock-services --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MIT. Keep the copyright notice and credit the authors.
corpus omeiza-workspace--api-mock-services · API design and specification
Related corpora: prism, markdownlint, sonukapoor/warpdom, bocmiao/api
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
omeiza-workspace/api-mock-services
Stand-ins for the outside world: the payment gateways, the email provider, the accounting service, the DNS provider, the messaging and the identity checks
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/omeiza-workspace)
Included with the author's permission (email, 2026-10-25), under each repository's own licence, with attribution. Own more repositories? Sign in with GitHub and add them. Want something removed? Reply to the email, withdraw it on /add, or open an issue on xerj-org/xerj.