Hi HN! I am a huge user of AI coding tools, especially Claude Code and Cursor, but every session starts fresh. It doesn't remember yesterday's architectural decision or know your team's coding patterns.
I built Cont3xt.dev to give Claude (and other AI tools) persistent access to team context via MCP.
*How it works:*
1. Document your team's context once (architectural decisions, coding standards, patterns)
2. When Claude Code (or Claude.ai, Cursor, etc.) needs context, it fetches relevant info via MCP
3. Claude generates code that actually matches your team's approach
*Example:* You: "Create a user service" Without context: Claude might use different patterns than your existing services With Cont3xt: Claude knows you use repository pattern, knows your error handling approach, follows your naming conventions
Travelling now is a complicated experience. Can you go to a country? What do you need to travel there? Are masks, quarantine and tests required? What is the situation like there - can you go to bars and beaches, can you do business there?
On top of this, the regulations are changing all the time. How can you be sure that the trip you booked in two or three months time will still be allowed? These questions aren't going away, each country has their own rules and risk levels. The uncertainty and overhead is real, and this is what the Travel Advice API looks to help with.
Using a simple API, you can get all the required information about a trip at your fingertips. Imagine booking a trip on AirBnB or Booking.com and having real time information about that destination shown to you. And then being able to opt in to notifications about any changes in your trip, allowing you to not worry and only need to amend arrangements when you are notified.
We've built the API to allow this for any website. The two products are direct API integration, and our User Itinerary Service. Direct API integration let's you use this information in your website or service how you want it to be used, giving the most value to your customers. The User Itinerary Service allows any customer to be pro-actively notified before and during their trip (one or multiple destinations) about any changes they need to be aware of.
We've just come out of our beta and are looking for feedback! We have loads of exciting features on the roadmap and the product will go from strength to strength through the coming months.
Hi HN! I wanted to find a good API for COVID19 data but the ones I came across seemed less than ideal. I hacked this together over a few hours and will be extending the routes as time goes on. Data is pulled from the Johns Hopkins CSSE github repo and will update daily.
The idea is for people to be able to use this to build graphs, mobile apps, etc.
I'm not sure banking can get away from the traditional. I like the idea of a blockchain (or some version of it) being implemented to assist in interbank communication.
Banks will probably only jump on BTC way down the line, if they ever do.
Since the VISA API seems of interest, MasterCard also has one. I wrote about a particular use case for these APIs, and other commercial ones, in a blog post [1].
TLDR: You need to be a "verified partner" or be sponsored to use VISA or MasterCard APIs.
In South Africa we have the same situation, no access to banking APIs so little room for innovation.
As a side project I decided to try and build banking infrastructure from the ground up, learning Go in the process [1], writing about the development along the way [2].
There is so much room for innovation in the traditional banking space, i.e. not using cryptocurrencies. Hopefully there will be innovation, especially when it comes to managing risk.
Thanks for the feedback. I think it's a lot more than that, picture drag and drop blog creation meets email. Because it sits on top of the normal email protocol, what it can deliver is significantly less restricted.
I built Cont3xt.dev to give Claude (and other AI tools) persistent access to team context via MCP.
*How it works:*
1. Document your team's context once (architectural decisions, coding standards, patterns)
2. When Claude Code (or Claude.ai, Cursor, etc.) needs context, it fetches relevant info via MCP
3. Claude generates code that actually matches your team's approach
*Example:* You: "Create a user service" Without context: Claude might use different patterns than your existing services With Cont3xt: Claude knows you use repository pattern, knows your error handling approach, follows your naming conventions
*Features:*
- Rules library (prioritised - critical rules always included)
- Architectural Decision Records (why you chose X over Y)
- Smart filtering (only relevant context, respects token budgets)
- Analytics (track what's actually useful)
Looking for beta testers and lots of feedback. Free during beta.