How is this better than using a separate chat for criticism?

Sessions run in complete isolation. Your main conversation stays clean—no copy-pasting, no context pollution. You get the insight without the mess.

What makes this different from just prompting Claude harder?

We inject structured tools that create auditable reasoning trails. "Be critical" is a suggestion. Our tools leave evidence.

Why does ChatGPT always agree with me?

AI models are trained to be helpful and avoid conflict, leading to sycophantic behavior. They validate your ideas instead of challenging them. Our tools use structured tool calls that force systematic evaluation, preventing the AI from simply agreeing.

How does billing work?

$20/month or $180/year for full access to all reasoning tools. Cancel anytime from your account settings. No usage metering, no overage charges.

Who actually uses this?

Mostly developers and technical founders using AI coding agents (Claude Code, Cursor, Windsurf). When the agent is on iteration 30 of the wrong approach, an isolated reasoning session breaks the loop.

What do you do with my data?

Your reasoning sessions are private and encrypted. We do not train models on your data. We do not sell or share your content. Sessions are stored only for you to access and reference.

Won't this slow me down?

The reasoning step takes seconds. Rewriting a hallucinated backend takes weeks. The fastest way to ship is to not build the wrong thing.

Accessibility Statement | reasoning.services

Our Commitment

Democratize Technology is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WCAG defines three levels of conformance: Level A, Level AA, and Level AAA.

reasoning.services is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard due to the known limitations listed below.

Known Limitations

Despite our best efforts, some content may not be fully accessible. The following known limitations are being addressed:

Colour contrast (some interface elements): Several design tokens do not meet the 4.5:1 minimum contrast ratio for normal text. Remediation is tracked in ADR-331.
API key management dialogs: The modal dialogs for creating and revoking API keys are being updated to include full ARIA dialog semantics, focus trapping, and Escape-key dismissal per WCAG 4.1.2.
Complex interactive tools: Some MCP reasoning tools may present large amounts of structured text that is optimised for sighted reading. All tool output is plain text and is readable by assistive technologies, but the visual layout may not convey hierarchy to screen readers in all cases.

If you encounter a barrier not listed here, please use the feedback mechanism below.

Feedback and Contact

We welcome your feedback on the accessibility of reasoning.services. Please let us know if you encounter accessibility barriers:

E-mail: accessibility@reasoning.services
Contact form: reasoning.services/contact

We aim to respond to accessibility feedback within 2 business days.

Formal Complaints

If you are not satisfied with our response to your accessibility concern, you may contact the relevant national or regional enforcement authority:

United States: U.S. Department of Justice, Civil Rights Division — ADA Information Line (1-800-514-0301)
European Union: Contact the national supervisory authority in your EU member state under the European Accessibility Act (Directive 2019/882).

Technical Specifications

Accessibility of reasoning.services relies on the following technologies to work with your browser and any assistive technologies or plugins installed:

HTML5
WAI-ARIA
CSS
JavaScript (ES2022+)

This site is designed to be compatible with the following assistive technologies:

VoiceOver (macOS / iOS)
NVDA (Windows)
JAWS (Windows)
TalkBack (Android)
Narrator (Windows)

Assessment Approach

Democratize Technology assessed the accessibility of reasoning.services by the following approaches:

Automated testing: Page-level and component-level accessibility audits run on every CI build using axe-core (jest-axe) per ADR-301.
Manual review: Keyboard navigation and screen-reader testing during feature development and on a scheduled basis.
External evaluation: Planned for future compliance cycles.

Our Services

reasoning.services hosts AI-powered reasoning tools delivered via the Model Context Protocol (MCP). All tools use a text-based input and output model — no audio, video, or visual-only content is required to use any service.

Structured Reflection: Multi-perspective analysis through guided text prompts
Sequential Thinking: Step-by-step reasoning with auditable decision trails
Context Switcher: Perspective-shifting analysis for complex problems
Decision Matrix: Systematic decision analysis with weighted scoring

How Our Services Work

All services accept plain text input and return plain text output. They are compatible with:

Screen readers: All tool output is text-based with no visual-only elements
Keyboard navigation: All controls are standard HTML elements reachable by Tab key
Browser zoom and text resizing: Responsive design supports up to 400% zoom without horizontal scrolling
High-contrast and forced-colour modes: CSS media queries respond to user colour preferences

Compliance Mapping

Requirement	Status	How Met
WCAG 2.1 Level AA	Partially conformant	Automated testing with axe-core; manual review. Known gaps listed above.
User preferences (EN 301 549 §11.7)	In progress	CSS media queries for `forced-colors`, `prefers-contrast`, `prefers-reduced-motion`
E-commerce accessibility (EAA Annex I §IV(g))	In progress	Accessible checkout flow, plan selection, and account management. ADR-317.
CEFR B2 readability (EAA Annex I §IV(e)(ii))	In progress	Readability audit of error messages, billing text, and account labels. ADR-318.

Quality Assurance

Automated accessibility testing in the CI/CD pipeline (jest-axe) on every build
Page-level accessibility tests for all routes per ADR-301
Annual manual review scheduled by accessibility specialists
Continuous feedback mechanism via the contact form and e-mail above

Date of Statement

This statement was created on May 7, 2026 following the W3C Developing an Accessibility Statement guidance.

This statement is reviewed annually or when significant accessibility changes occur.

Navigation

Accessibility Statement